← previous blocknext block →recent activity
Analyzing
Block #106,100,478
11 transactions · 10 stateful · 2026-09-19 06:02:43 UTC
Parallelism
64/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,100,478 · 11 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
2w03w16w29w310w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x51fc8795…126f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x9057e0ca…fb47
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x045532dd…4b7d
0x34b655…2a6f
4 touches
1 conflict
0x0f13b598…f75b
0x34b655…2a6f
2 touches
0 conflicts
0x2249932e…474a
0x34b655…2a6f
2 touches
0 conflicts
0x24ed774e…bd89
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x51fc8795c8…57126f
Audit this contract →
← previous block·next block →recent activity