← previous blocknext block →recent activity
Analyzing
Block #101,986,251
17 transactions · 15 stateful · 2026-09-04 19:42:11 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #101,986,251 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w011w112w215w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd713bab…a651
0x34b655…2a6f
8 touches
6 conflicts
0x3d13406e…eff1
0x34b655…2a6f
8 touches
6 conflicts
0x53e08444…d671
0x34b655…2a6f
8 touches
6 conflicts
0x7c216fca…20cb
0x34b655…2a6f
8 touches
6 conflicts
0x8bf661cb…bcd2
0x34b655…2a6f
8 touches
6 conflicts
0x8dfa3fd4…d3a1
0x34b655…2a6f
8 touches
6 conflicts
0x999c658d…b185
0x34b655…2a6f
8 touches
6 conflicts
0xc52785b9…08f8
0x34b655…2a6f
8 touches
6 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
6 conflicts on slot 0xfd713bab1a…98a651
Audit this contract →
← previous block·next block →recent activity