← previous blocknext block →recent activity
Analyzing
Block #96,154,560
7 transactions · 7 stateful · 2026-08-15 08:22:12 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,154,560 · 7 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc3baa205…f26e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x85e59464…9104
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x2b46c0…1669
2 touches
0 conflicts
0x8cf3d245…1d0d
0x2b46c0…1669
2 touches
0 conflicts
0xb05cd4f5…73d0
0x2b46c0…1669
2 touches
0 conflicts
0xdb067026…9eb8
0x2b46c0…1669
2 touches
0 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
1 conflict on slot 0xc3baa205b9…b3f26e
Audit this contract →
← previous block·next block →recent activity