← previous blocknext block →recent activity
Analyzing
Block #95,797,991
14 transactions · 11 stateful · 2026-08-14 02:28:11 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,797,991 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w29w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4efe356f…22fa
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x4c619b7d…f4fa
0x34b655…2a6f
6 touches
3 conflicts
0xd895ee0b…d301
0x34b655…2a6f
4 touches
1 conflict
0x819d93e2…aa4a
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
0x34b655…2a6f
4 touches
1 conflict
0x839becaf…e149
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x4efe356fb8…ca22fa
Audit this contract →
← previous block·next block →recent activity