← previous blocknext block →recent activity
Analyzing
Block #95,349,963
37 transactions · 32 stateful · 2026-08-12 12:51:13 UTC
Parallelism
68/100
Blocked
63%
Avg conflicts / tx
1.43
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #95,349,963 · 37 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
2w03w14w26w07w18w29w310w417w521w726w329w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x89678d1b…463e
0xa6afd3…d132
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xa1ff0729…0146
0xa6afd3…d132
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
10 conflicts on slot 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity