← previous blocknext block →recent activity
Analyzing
Block #106,192,469
17 transactions · 17 stateful · 2026-09-19 13:45:41 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,192,469 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w26w07w19w012w013w114w215w316w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049b2aa8…3a46
0x6f6493…b480
7 touches
6 conflicts
0x06e88bfa…4921
0x6f6493…b480
7 touches
6 conflicts
0x147b88c5…3fce
0x6f6493…b480
7 touches
6 conflicts
0x23269dfa…ce4f
0x6f6493…b480
7 touches
6 conflicts
0x284f0bd8…eaa1
0x6f6493…b480
7 touches
6 conflicts
0x38847cdc…8648
0x6f6493…b480
7 touches
6 conflicts
0x38feb3fa…f374
0x6f6493…b480
7 touches
6 conflicts
0x3c677056…47d0
0x6f6493…b480
7 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: 0x6f6493e3…08b480
6 conflicts on slot 0x049b2aa85d…073a46
Audit this contract →
← previous block·next block →recent activity