← previous blocknext block →recent activity
Analyzing
Block #95,646,951
22 transactions · 22 stateful · 2026-08-13 13:47:29 UTC
Parallelism
77/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,646,951 · 22 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
2w03w14w05w18w112w217w018w119w220w321w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6cc7dad6…8ded
0x34b655…2a6f
6 touches
3 conflicts
0x38a06385…ed6a
0x34b655…2a6f
6 touches
3 conflicts
0x9d9bed71…d466
0x34b655…2a6f
6 touches
3 conflicts
0xa771fb55…48d2
0x34b655…2a6f
6 touches
3 conflicts
0x1683d146…5ec2
0x34b655…2a6f
4 touches
1 conflict
0x5d3bb355…4549
0x34b655…2a6f
4 touches
1 conflict
0x5fde4971…aac9
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity