← previous blocknext block →recent activity
Analyzing
Block #85,136,701
20 transactions · 18 stateful · 2026-07-02 15:12:54 UTC
Parallelism
80/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,136,701 · 20 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
2w03w15w06w110w211w214w015w119w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb04d17a0…10e8
0x34b655…2a6f
6 touches
3 conflicts
0xa9988419…9f45
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0x04fdea…47d7
4 touches
1 conflict
0x3230277c…ef39
0xc8689a…ee79
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x6c1fdf6c…3805
0x40c49f…2af0
2 touches
0 conflicts
0x6d90ded0…1ecd
0x40c49f…2af0
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 0xb04d17a0fe…4810e8
Audit this contract →
← previous block·next block →recent activity