← previous blocknext block →recent activity
Analyzing
Block #106,367,606
20 transactions · 14 stateful · 2026-09-20 04:27:09 UTC
Parallelism
90/100
Blocked
29%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,367,606 · 20 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w07w18w19w012w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2130a548…c1de
0x34b655…2a6f
4 touches
1 conflict
0x4681609f…6493
0x34b655…2a6f
4 touches
1 conflict
0xc86aea27…5791
0x34b655…2a6f
4 touches
1 conflict
0xc96ccb33…491f
0x34b655…2a6f
4 touches
1 conflict
0xd86e9146…3d0b
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0xaad6be10…0801
0x2a68ba…90c5
4 touches
1 conflict
0x0262e1c6…52e1
0x34b655…2a6f
4 touches
1 conflict
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 0x2130a548b9…31c1de
Audit this contract →
← previous block·next block →recent activity