← previous blocknext block →recent activity
Analyzing
Block #95,654,037
20 transactions · 18 stateful · 2026-08-13 14:23:07 UTC
Parallelism
70/100
Blocked
50%
Avg conflicts / tx
1.45
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,654,037 · 20 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
2w03w04w15w26w37w48w59w010w113w214w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0031
0x59df86…2780
12 touches
15 conflicts
0x3b9bb58c…e73a
0x34b655…2a6f
8 touches
6 conflicts
0x726fb2f9…2d8d
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x49611dcc…9864
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xb0608dfe…083d
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: 0x59df8637…6d2780
15 conflicts on slot 0x0000000000…000031
Audit this contract →
← previous block·next block →recent activity