← previous blocknext block →recent activity
Analyzing
Block #106,420,492
25 transactions · 24 stateful · 2026-09-20 08:53:18 UTC
Parallelism
76/100
Blocked
33%
Avg conflicts / tx
0.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #106,420,492 · 25 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
1w04w06w010w117w118w120w121w222w323w424w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa8d9cec7…043e
0x34b655…2a6f
10 touches
10 conflicts
0x5e1c23e9…4f81
0x34b655…2a6f
10 touches
10 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
6 touches
3 conflicts
0x810a3aa2…0227
0x34b655…2a6f
6 touches
3 conflicts
0x0463db49…5d05
0x34b655…2a6f
4 touches
1 conflict
0x1785cf5f…58ba
0x34b655…2a6f
4 touches
1 conflict
0x1b25f260…c429
0x34b655…2a6f
4 touches
1 conflict
0x340926f0…8de2
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 0xa8d9cec734…d6043e
Audit this contract →
← previous block·next block →recent activity