← previous blocknext block →recent activity
Analyzing
Block #96,602,586
17 transactions · 16 stateful · 2026-08-16 21:55:52 UTC
Parallelism
59/100
Blocked
50%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,602,586 · 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
1w02w13w24w35w17w48w29w010w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x34724223…fd0f
0x34b655…2a6f
6 touches
3 conflicts
0x5ef698c5…5ce4
0x34b655…2a6f
4 touches
1 conflict
0x775a8ad3…8307
0x34b655…2a6f
4 touches
1 conflict
0x79adeae4…34ff
0x34b655…2a6f
4 touches
1 conflict
0x7e880119…f5e9
0x34b655…2a6f
4 touches
1 conflict
0x818e1296…f4d7
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
21 conflicts on slot 0x2d65195682…4112e8
Audit this contract →
← previous block·next block →recent activity