← previous blocknext block →recent activity
Analyzing
Block #106,366,946
16 transactions · 16 stateful · 2026-09-20 04:23:49 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,366,946 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w17w18w29w310w211w312w413w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x55a7c54b…bdcc
0x34b655…2a6f
10 touches
10 conflicts
0x3cc04064…aa09
0x34b655…2a6f
10 touches
10 conflicts
0x3cb7ee74…b8a5
0x34b655…2a6f
8 touches
6 conflicts
0x574628e9…dcc3
0x34b655…2a6f
6 touches
3 conflicts
0xa60eabc0…9f8c
0x34b655…2a6f
6 touches
3 conflicts
0x2c2761c0…476e
0x34b655…2a6f
6 touches
3 conflicts
0xfdd131fa…dbdb
0x34b655…2a6f
6 touches
3 conflicts
0x54f7f60f…43cc
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
10 conflicts on slot 0x55a7c54b6f…4fbdcc
Audit this contract →
← previous block·next block →recent activity