← previous blocknext block →recent activity
Analyzing
Block #95,246,243
12 transactions · 12 stateful · 2026-08-12 04:02:24 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,246,243 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w27w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x19795ad6…4a16
0x34b655…2a6f
6 touches
3 conflicts
0xe2d97470…defd
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0xf61165ef…adb9
0x34b655…2a6f
4 touches
1 conflict
0x5ec20bc2…fafa
0x34b655…2a6f
4 touches
1 conflict
0x5f252331…acd0
0x34b655…2a6f
4 touches
1 conflict
0x08636046…e60f
0x34b655…2a6f
4 touches
1 conflict
0x96dd83e6…a507
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
3 conflicts on slot 0x19795ad604…434a16
Audit this contract →
← previous block·next block →recent activity