← previous blocknext block →recent activity
Analyzing
Block #96,513,134
5 transactions · 5 stateful · 2026-08-16 14:25:58 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.4
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,513,134 · 5 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xbf2c6707…4cbd
0x34b655…2a6f
4 touches
1 conflict
0xe467d3df…2421
0x34b655…2a6f
4 touches
1 conflict
0x00d75bbb…13e8
0x34b655…2a6f
4 touches
1 conflict
0x0313aedc…bfaf
0x34b655…2a6f
4 touches
1 conflict
0x0313aedc…bfb0
0x34b655…2a6f
4 touches
1 conflict
0x35ac559a…9b80
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 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity