← previous blocknext block →recent activity
Analyzing
Block #95,522,564
17 transactions · 14 stateful · 2026-08-13 03:21:50 UTC
Parallelism
88/100
Blocked
21%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,522,564 · 17 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
5w06w17w08w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x45f6e0e6…2c9a
0x34b655…2a6f
4 touches
1 conflict
0x86cea35b…bdff
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x735a3dc0…fbd3
0xd32edf…ff58
3 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x7ca37811…f3b3
0x065c9d…c394
2 touches
0 conflicts
0x524f0872…0d12
0x34b655…2a6f
2 touches
0 conflicts
0x71cc73a0…d523
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 0x45f6e0e68e…372c9a
Audit this contract →
← previous block·next block →recent activity