← previous blocknext block →recent activity
Analyzing
Block #95,810,351
10 transactions · 9 stateful · 2026-08-14 03:30:21 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,810,351 · 10 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
1w02w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe10ec9db…b75e
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
4 touches
1 conflict
0x948836ff…59ab
0x34b655…2a6f
4 touches
1 conflict
0x961c0cd9…0937
0x34b655…2a6f
4 touches
1 conflict
0x73eefb08…6ca5
0x34b655…2a6f
4 touches
1 conflict
0x09c972e9…8057
0x34b655…2a6f
3 touches
1 conflict
0x4be9812b…48a9
0x34b655…2a6f
2 touches
0 conflicts
0x681653cc…9cdb
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
3 conflicts on slot 0xe10ec9db19…25b75e
Audit this contract →
← previous block·next block →recent activity