← previous blocknext block →recent activity
Analyzing
Block #96,284,061
10 transactions · 8 stateful · 2026-08-15 19:13:32 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,284,061 · 10 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
2w03w15w16w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7938c6fd…1cd1
0x34b655…2a6f
4 touches
1 conflict
0x9fd372a1…a959
0x34b655…2a6f
4 touches
1 conflict
0xa3ed5a09…c6d3
0x34b655…2a6f
4 touches
1 conflict
0x06726618…fafd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf40e9839…0001
0x34b655…2a6f
4 touches
1 conflict
0xfe5db881…7a38
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 0x7938c6fdb8…841cd1
Audit this contract →
← previous block·next block →recent activity