← previous blocknext block →recent activity
Analyzing
Block #96,088,829
11 transactions · 6 stateful · 2026-08-15 02:51:32 UTC
Parallelism
73/100
Blocked
33%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,088,829 · 11 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
4w05w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x177d036a…1c5d
0x34b655…2a6f
4 touches
1 conflict
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0daa48d2…1cdd
0x34b655…2a6f
2 touches
0 conflicts
0x0ddfdaf2…9e00
0x34b655…2a6f
2 touches
0 conflicts
0x1060d138…b6a5
0x34b655…2a6f
2 touches
0 conflicts
0x1060d138…b6a6
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 0x177d036a8b…531c5d
Audit this contract →
← previous block·next block →recent activity