← previous blocknext block →recent activity
Analyzing
Block #85,190,967
15 transactions · 15 stateful · 2026-07-02 21:14:17 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.6
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,190,967 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w110w211w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd63e616b…a07d
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x307d4d49…6f08
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x6db97e95…8353
0x34b655…2a6f
4 touches
1 conflict
0x6f7a92ed…5651
0x34b655…2a6f
4 touches
1 conflict
0x785fa71b…b834
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
6 conflicts on slot 0xd63e616b67…7fa07d
Audit this contract →
← previous block·next block →recent activity