← previous blocknext block →recent activity
Analyzing
Block #85,105,362
31 transactions · 19 stateful · 2026-07-02 11:43:24 UTC
Parallelism
77/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,105,362 · 31 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w06w07w19w211w212w325w326w427w528w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x79b3209b…f766
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x03b80343…8781
0x34b655…2a6f
4 touches
1 conflict
0x53cccb07…d7f0
0x34b655…2a6f
4 touches
1 conflict
0x57a080db…7fde
0x34b655…2a6f
4 touches
1 conflict
0x58397d66…a6bc
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity