← previous blocknext block →recent activity
Analyzing
Block #96,591,788
6 transactions · 6 stateful · 2026-08-16 21:01:34 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,591,788 · 6 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
4 touches
1 conflict
0x07010ea7…c45a
0x34b655…2a6f
2 touches
0 conflicts
0x0f6aef87…8137
0x34b655…2a6f
2 touches
0 conflicts
0x1b4fa1a0…7d7b
0x34b655…2a6f
2 touches
0 conflicts
0x2bb0d58d…9dcf
0x34b655…2a6f
2 touches
0 conflicts
0x303c6660…6aa1
0x34b655…2a6f
2 touches
0 conflicts
0x304f4cbc…b4fa
0x34b655…2a6f
2 touches
0 conflicts
0x3074de0b…2a60
0x34b655…2a6f
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 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity