← previous blocknext block →recent activity
Analyzing
Block #96,536,723
10 transactions · 8 stateful · 2026-08-16 16:24:36 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,536,723 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w14w05w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x957c875f…b3f9
0x34b655…2a6f
4 touches
1 conflict
0x968880bc…944e
0x34b655…2a6f
4 touches
1 conflict
0xaf1352f4…49be
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x1a69c7c5…09cc
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
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 0x957c875f2a…99b3f9
Audit this contract →
← previous block·next block →recent activity