← previous blocknext block →recent activity
Analyzing
Block #85,618,481
14 transactions · 13 stateful · 2026-07-04 20:41:24 UTC
Parallelism
71/100
Blocked
31%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,618,481 · 14 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
1w05w06w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0xdc746738…0698
0x34b655…2a6f
6 touches
3 conflicts
0x2a9092cb…64ee
0x34b655…2a6f
3 touches
1 conflict
0xc0088a6f…35d6
0xd32edf…ff58
3 touches
1 conflict
0x66de0ce3…337a
0x188d58…ea8e
2 touches
0 conflicts
0x66de0ce3…337c
0x188d58…ea8e
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity