← previous blocknext block →recent activity
Analyzing
Block #85,198,559
18 transactions · 17 stateful · 2026-07-02 22:04:53 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,198,559 · 18 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
4w06w111w012w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xd63e616b…a07d
0x34b655…2a6f
8 touches
6 conflicts
0xb44564d6…bb43
0x34b655…2a6f
8 touches
6 conflicts
0x9a36c85b…96a5
0x34b655…2a6f
6 touches
3 conflicts
0x300fdb70…eabe
0x34b655…2a6f
6 touches
3 conflicts
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x602cc01e…0b5e
0x34b655…2a6f
4 touches
1 conflict
0x680fdd59…e84d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity