← previous blocknext block →recent activity
Analyzing
Block #95,724,655
15 transactions · 9 stateful · 2026-08-13 20:19:22 UTC
Parallelism
87/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,724,655 · 15 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
6w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdbd174e4…b6f8
0x34b655…2a6f
4 touches
1 conflict
0x9c2e6ea0…9df8
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0fb9e50c…1a35
0x34b655…2a6f
2 touches
0 conflicts
0x342222e8…2ec4
0x34b655…2a6f
2 touches
0 conflicts
0x4d4389b2…6e07
0x34b655…2a6f
2 touches
0 conflicts
0x57267d66…dda6
0x34b655…2a6f
2 touches
0 conflicts
0x5f72d58f…c445
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 0xdbd174e4dd…5cb6f8
Audit this contract →
← previous block·next block →recent activity