← previous blocknext block →recent activity
Analyzing
Block #96,283,060
14 transactions · 13 stateful · 2026-08-15 19:08:30 UTC
Parallelism
64/100
Blocked
54%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,283,060 · 14 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
2w03w06w17w18w29w311w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa5a8ffca…8de2
0x34b655…2a6f
8 touches
6 conflicts
0x1c097b81…0164
0x34b655…2a6f
6 touches
3 conflicts
0x1c5359ff…8582
0x34b655…2a6f
6 touches
3 conflicts
0x30e89ce7…7d4b
0x34b655…2a6f
6 touches
3 conflicts
0x424934c8…f2f1
0x34b655…2a6f
6 touches
3 conflicts
0x4839b308…9cdb
0x34b655…2a6f
6 touches
3 conflicts
0x52b065b2…d503
0x34b655…2a6f
6 touches
3 conflicts
0x5adda4a7…b840
0x34b655…2a6f
6 touches
3 conflicts
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
6 conflicts on slot 0xa5a8ffca31…818de2
Audit this contract →
← previous block·next block →recent activity