← previous blocknext block →recent activity
Analyzing
Block #106,199,481
40 transactions · 36 stateful · 2026-09-19 14:20:58 UTC
Parallelism
80/100
Blocked
75%
Avg conflicts / tx
2.05
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #106,199,481 · 40 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w26w37w48w59w410w013w015w117w118w219w321w422w523w631w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dd96c96…7335
0x34b655…2a6f
14 touches
21 conflicts
0x51fc8795…126f
0x34b655…2a6f
14 touches
21 conflicts
0xb75367ff…a2b7
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf47769ab…0d08
0x34b655…2a6f
14 touches
21 conflicts
0xd17580f9…ece1
0x754704…b603
12 touches
15 conflicts
0x045532dd…4b7d
0x34b655…2a6f
12 touches
15 conflicts
0xd5331c78…1751
0xd32edf…ff58
11 touches
15 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 0x7dd96c965e…857335
Audit this contract →
← previous block·next block →recent activity