← previous blocknext block →recent activity
Analyzing
Block #96,605,256
19 transactions · 19 stateful · 2026-08-16 22:09:19 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.37
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,605,256 · 19 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
1w02w13w24w35w36w47w512w418w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d651956…12e8
0x34b655…2a6f
14 touches
21 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0xdf0b4e17…ccd8
0x34b655…2a6f
6 touches
3 conflicts
0x9c574ff9…2fb8
0x34b655…2a6f
6 touches
3 conflicts
0xf039e2f8…3d8a
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x2ed336a4…72b1
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