← previous blocknext block →recent activity
Analyzing
Block #95,414,303
8 transactions · 7 stateful · 2026-08-12 18:17:03 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,414,303 · 8 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc53838dd…85c9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc22a0c80…6c90
0x34b655…2a6f
4 touches
1 conflict
0x39916c0e…9220
0x34b655…2a6f
2 touches
0 conflicts
0x48203298…65cb
0x34b655…2a6f
2 touches
0 conflicts
0x4f394483…ff62
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 0xc53838ddd7…b885c9
Audit this contract →
← previous block·next block →recent activity