← previous blocknext block →recent activity
Analyzing
Block #85,190,557
13 transactions · 10 stateful · 2026-07-02 21:11:34 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.15
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,190,557 · 13 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
1w02w15w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x7e1c758b…2f47
0x34b655…2a6f
4 touches
1 conflict
0xb7eebf04…eef8
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0efc210e…70ab
0x34b655…2a6f
4 touches
1 conflict
0x5d7e3566…e582
0x34b655…2a6f
4 touches
1 conflict
0xa1706b7b…c1a7
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
1 conflict on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity