← previous blocknext block →recent activity
Analyzing
Block #105,843,281
25 transactions · 24 stateful · 2026-09-18 08:27:12 UTC
Parallelism
72/100
Blocked
54%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #105,843,281 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w17w08w110w011w012w113w214w315w416w517w621w222w323w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb9d24b27…d1f2
0x34b655…2a6f
14 touches
21 conflicts
0x8db32935…81a7
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x5e3014f0…b4e1
0x34b655…2a6f
10 touches
10 conflicts
0x5fad6fee…7714
0x34b655…2a6f
10 touches
10 conflicts
0x8999c339…d325
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x51fc8795…126f
0x34b655…2a6f
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Perpl
21 conflicts on slot 0xb9d24b2742…53d1f2
Audit this contract →
← previous block·next block →recent activity