← previous blocknext block →recent activity
Analyzing
Block #106,185,826
12 transactions · 12 stateful · 2026-09-19 13:12:15 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #106,185,826 · 12 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
1w02w13w07w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x1cdfe548…d3aa
0x34b655…2a6f
6 touches
3 conflicts
0x92fa1dc0…b239
0x34b655…2a6f
6 touches
3 conflicts
0x8f7dfe8c…3fe8
0x34b655…2a6f
6 touches
3 conflicts
0xfd9bfada…b65b
0x34b655…2a6f
6 touches
3 conflicts
0x786d66ce…ae70
0x34b655…2a6f
5 touches
3 conflicts
0x40a9339c…6571
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity