← previous blocknext block →recent activity
Analyzing
Block #96,568,777
11 transactions · 11 stateful · 2026-08-16 19:05:49 UTC
Parallelism
73/100
Blocked
45%
Avg conflicts / tx
0.82
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,568,777 · 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
1w02w13w25w06w07w18w210w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe6707a4…2c3c
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x446f2734…8b54
0x0a3323…0a3c
6 touches
3 conflicts
0x52c63247…ce02
0x0a3323…0a3c
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x0dd3bdfb…7537
0x34b655…2a6f
4 touches
1 conflict
0x0dd3bdfb…7538
0x34b655…2a6f
4 touches
1 conflict
0x3522af60…d679
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 0xbe6707a406…4e2c3c
Audit this contract →
← previous block·next block →recent activity