← previous blocknext block →recent activity
Analyzing
Block #96,481,868
9 transactions · 7 stateful · 2026-08-16 11:48:24 UTC
Parallelism
56/100
Blocked
43%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,481,868 · 9 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
1w03w14w25w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf90c6521…d8f0
0x34b655…2a6f
4 touches
1 conflict
0x4174fdf9…fcfd
0x34b655…2a6f
4 touches
1 conflict
0x757b0543…e087
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc3830032…0e9d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
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
1 conflict on slot 0xf90c6521bf…2dd8f0
Audit this contract →
← previous block·next block →recent activity