← previous blocknext block →recent activity
Analyzing
Block #96,374,681
9 transactions · 8 stateful · 2026-08-16 02:49:19 UTC
Parallelism
56/100
Blocked
50%
Avg conflicts / tx
0.56
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,374,681 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd5d0b681…ca6c
0x34b655…2a6f
6 touches
3 conflicts
0xf5c92564…4d35
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xcd6a810f…561e
0x34b655…2a6f
4 touches
1 conflict
0xcf8e8419…c691
0x34b655…2a6f
4 touches
1 conflict
0xd6113c0f…0a4b
0x34b655…2a6f
4 touches
1 conflict
0x0b1a9431…183e
0x34b655…2a6f
4 touches
1 conflict
0x0fe1e6e0…f553
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 0xd5d0b68121…6aca6c
Audit this contract →
← previous block·next block →recent activity