← previous blocknext block →recent activity
Analyzing
Block #95,268,766
13 transactions · 11 stateful · 2026-08-12 06:00:27 UTC
Parallelism
62/100
Blocked
45%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #95,268,766 · 13 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
1w02w13w04w15w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68661b81…6fcb
0x34b655…2a6f
8 touches
6 conflicts
0xe0e00683…e335
0x34b655…2a6f
8 touches
6 conflicts
0xe2c9bbaf…20cb
0x34b655…2a6f
4 touches
1 conflict
0xd800e635…b1d7
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xa6176fff…d2c5
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
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 0x68661b81cd…436fcb
Audit this contract →
← previous block·next block →recent activity