← previous blocknext block →recent activity
Analyzing
Block #95,269,263
10 transactions · 10 stateful · 2026-08-12 06:02:57 UTC
Parallelism
80/100
Blocked
10%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,269,263 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe969b395…ceea
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d8
0x34b655…2a6f
4 touches
1 conflict
0x367b69ad…33d9
0x34b655…2a6f
4 touches
1 conflict
0x3a5e95ba…806a
0x34b655…2a6f
4 touches
1 conflict
0x53d526f9…1ab8
0x34b655…2a6f
4 touches
1 conflict
0x5923bca7…b54f
0x34b655…2a6f
4 touches
1 conflict
0x63c2f212…ebc3
0x34b655…2a6f
4 touches
1 conflict
0x30ae635d…5e67
0x34b655…2a6f
2 touches
0 conflicts
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 0xe969b39585…d4ceea
Audit this contract →
← previous block·next block →recent activity