← previous blocknext block →recent activity
Analyzing
Block #96,838,126
16 transactions · 14 stateful · 2026-08-17 17:40:33 UTC
Parallelism
69/100
Blocked
50%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,838,126 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w25w36w18w09w110w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07cd985e…a0ea
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x0bc80bb4…a97c
0x851145…3f07
4 touches
1 conflict
0xe6e6f436…ddc0
0x34b655…2a6f
4 touches
1 conflict
0xe9991812…e391
0x34b655…2a6f
4 touches
1 conflict
0xf2b035ef…4746
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
4 touches
1 conflict
0x22e0cc1d…ad0d
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
3 conflicts on slot 0x07cd985ec2…60a0ea
Audit this contract →
← previous block·next block →recent activity