← previous blocknext block →recent activity
Analyzing
Block #106,403,611
12 transactions · 12 stateful · 2026-09-20 07:28:21 UTC
Parallelism
83/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,403,611 · 12 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
2w03w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xba392f8a…0867
0x34b655…2a6f
4 touches
1 conflict
0x02fa927d…6468
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x71f4e95f…8e98
0xa6afd3…d132
4 touches
1 conflict
0x8b52b75c…8a0d
0xa6afd3…d132
4 touches
1 conflict
0xcf2116ea…ad62
0xa6afd3…d132
3 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
2 touches
0 conflicts
0xd008ea29…1ff0
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 0xba392f8a96…ce0867
Audit this contract →
← previous block·next block →recent activity