← previous blocknext block →recent activity
Analyzing
Block #85,615,493
9 transactions · 8 stateful · 2026-07-04 20:21:27 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,615,493 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0xd8834cf3…0004
0x34b655…2a6f
4 touches
1 conflict
0x002dfab7…aa48
0x34b655…2a6f
2 touches
0 conflicts
0x1627c587…e8a9
0x34b655…2a6f
2 touches
0 conflicts
0x2007b9af…3c71
0x34b655…2a6f
2 touches
0 conflicts
0x49fc2bf5…7d91
0x34b655…2a6f
2 touches
0 conflicts
0x5a3e3430…7e44
0x34b655…2a6f
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
1 conflict on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity