← previous blocknext block →recent activity
Analyzing
Block #95,370,643
21 transactions · 19 stateful · 2026-08-12 14:36:02 UTC
Parallelism
76/100
Blocked
37%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,370,643 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w18w210w311w415w116w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe90b7bce…c2e0
0xfa32f9…f3f0
8 touches
6 conflicts
0x00000000…0000
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0002
0x116e7d…d8f1
8 touches
6 conflicts
0x00000000…0003
0x116e7d…d8f1
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x692a4122…76b8
0x350035…7777
8 touches
6 conflicts
0x99f666e3…b2a2
0x3bd359…433a
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: 0xfa32f9ec…fef3f0
6 conflicts on slot 0xe90b7bceb6…a7c2e0
Audit this contract →
← previous block·next block →recent activity