← previous blocknext block →recent activity
Analyzing
Block #95,160,877
19 transactions · 19 stateful · 2026-08-11 20:49:02 UTC
Parallelism
68/100
Blocked
37%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,160,877 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w48w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x734ee320…caae
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x4783345c…4a90
0x34b655…2a6f
4 touches
1 conflict
0x2a6ce996…6902
0x34b655…2a6f
4 touches
1 conflict
0x401a563c…0ae7
0x34b655…2a6f
4 touches
1 conflict
0x58d0a23c…5d3a
0x34b655…2a6f
4 touches
1 conflict
0x5edb8bbe…bc75
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
15 conflicts on slot 0x734ee32053…cecaae
Audit this contract →
← previous block·next block →recent activity