← previous blocknext block →recent activity
Analyzing
Block #96,030,725
19 transactions · 14 stateful · 2026-08-14 21:59:16 UTC
Parallelism
74/100
Blocked
43%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,030,725 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w17w211w015w316w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abaedb1…65b9
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x3c3a94ab…902b
0x34b655…2a6f
4 touches
1 conflict
0x427c9fc4…5cee
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x71e1dee6…d11b
0x34b655…2a6f
4 touches
1 conflict
0x81ca8c9e…28cb
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 0x4abaedb12b…3665b9
Audit this contract →
← previous block·next block →recent activity