← previous blocknext block →recent activity
Analyzing
Block #95,246,318
28 transactions · 25 stateful · 2026-08-12 04:03:05 UTC
Parallelism
64/100
Blocked
44%
Avg conflicts / tx
1.68
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #95,246,318 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w310w412w513w614w715w816w926w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
18 touches
36 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
18 touches
36 conflicts
0x49611dcc…9864
0x34b655…2a6f
12 touches
15 conflicts
0x8f203394…f2dc
0x34b655…2a6f
10 touches
10 conflicts
0x8f203394…f2db
0x34b655…2a6f
10 touches
10 conflicts
0x0b05d77e…6f90
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7be3246e…f89f
0x34b655…2a6f
6 touches
3 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
36 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity