← previous blocknext block →recent activity
Analyzing
Block #96,263,139
14 transactions · 9 stateful · 2026-08-15 17:28:18 UTC
Parallelism
86/100
Blocked
44%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,263,139 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w15w06w19w010w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe7bd356d…d23b
0x34b655…2a6f
4 touches
1 conflict
0xb3826464…b02d
0x34b655…2a6f
4 touches
1 conflict
0xbbe8fc78…c38b
0x34b655…2a6f
4 touches
1 conflict
0xbfca3cd0…5023
0x34b655…2a6f
4 touches
1 conflict
0xcc3678e9…76f7
0x34b655…2a6f
4 touches
1 conflict
0xd0919e62…a2a8
0x34b655…2a6f
4 touches
1 conflict
0xe7bd356d…d23a
0x34b655…2a6f
4 touches
1 conflict
0x1844c7a5…fa85
0x065c9d…c394
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
1 conflict on slot 0xe7bd356dd3…abd23b
Audit this contract →
← previous block·next block →recent activity