← previous blocknext block →recent activity
Analyzing
Block #85,195,073
16 transactions · 15 stateful · 2026-07-02 21:41:39 UTC
Parallelism
88/100
Blocked
27%
Avg conflicts / tx
0.44
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,195,073 · 16 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
1w03w05w07w08w110w011w113w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdc8d4ee0…def3
0x34b655…2a6f
4 touches
1 conflict
0xe2ca9bf2…8da8
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0x094bc502…09fd
0x34b655…2a6f
4 touches
1 conflict
0x159b8597…48a4
0x34b655…2a6f
4 touches
1 conflict
0x1a6b3787…a9e6
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
1 conflict on slot 0xdc8d4ee099…56def3
Audit this contract →
← previous block·next block →recent activity