← previous blocknext block →recent activity
Analyzing
Block #106,480,646
9 transactions · 9 stateful · 2026-09-20 13:56:05 UTC
Parallelism
78/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,480,646 · 9 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
1w03w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3cba0bdf…449f
0x34b655…2a6f
4 touches
1 conflict
0xc9d92517…c787
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x9327d918…2a0a
0x34b655…2a6f
4 touches
1 conflict
0x173b64af…6c43
0x34b655…2a6f
2 touches
0 conflicts
0x2492cf96…0f5b
0x34b655…2a6f
2 touches
0 conflicts
0x3948878d…28df
0x34b655…2a6f
2 touches
0 conflicts
0x3d13406e…eff1
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 0x3cba0bdf0d…56449f
Audit this contract →
← previous block·next block →recent activity