← previous blocknext block →recent activity
Analyzing
Block #96,824,640
15 transactions · 12 stateful · 2026-08-17 16:32:43 UTC
Parallelism
73/100
Blocked
42%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,824,640 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w18w29w313w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xfe65bb7b…12d7
0x34b655…2a6f
4 touches
1 conflict
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x352cdf9c…2863
0x34b655…2a6f
4 touches
1 conflict
0x4984f7be…d515
0x34b655…2a6f
4 touches
1 conflict
0x50e463a7…fafc
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x833f3561…bfd0
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 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity