← previous blocknext block →recent activity
Analyzing
Block #95,575,600
14 transactions · 14 stateful · 2026-08-13 07:48:35 UTC
Parallelism
86/100
Blocked
7%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,575,600 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x28ceceef…ecc2
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x6e6a8155…9636
0x34b655…2a6f
2 touches
0 conflicts
0x6f8368a9…8eb1
0x34b655…2a6f
2 touches
0 conflicts
0x9efc3d5b…9ab7
0x34b655…2a6f
2 touches
0 conflicts
0xcba9da8e…d898
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0x28ceceefb3…22ecc2
Audit this contract →
← previous block·next block →recent activity