← previous blocknext block →recent activity
Analyzing
Block #95,247,063
26 transactions · 22 stateful · 2026-08-12 04:08:25 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
2.31
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #95,247,063 · 26 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w37w48w510w611w712w814w915w1016w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6bb86299…6fb4
0x34b655…2a6f
18 touches
36 conflicts
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
14 touches
21 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x7be3246e…f89f
0x34b655…2a6f
8 touches
6 conflicts
0x80398c66…f3cc
0x34b655…2a6f
8 touches
6 conflicts
0x118c1867…8519
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6426
0x34b655…2a6f
8 touches
6 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 0x6bb8629904…526fb4
Audit this contract →
← previous block·next block →recent activity