← previous blocknext block →recent activity
Analyzing
Block #95,000,434
20 transactions · 20 stateful · 2026-08-11 07:21:09 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #95,000,434 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w110w411w512w616w619w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
14 touches
21 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x7cddbfcb…0d29
0x34b655…2a6f
4 touches
1 conflict
0x9da42530…1c86
0x34b655…2a6f
4 touches
1 conflict
0xb3650560…2747
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
21 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity