← previous blocknext block →recent activity
Analyzing
Block #85,990,610
25 transactions · 23 stateful · 2026-07-06 14:01:50 UTC
Parallelism
76/100
Blocked
35%
Avg conflicts / tx
0.52
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,990,610 · 25 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
2w03w15w07w08w09w112w113w118w219w322w423w5
- 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
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x5571e830…9cea
0x34b655…2a6f
4 touches
1 conflict
0x59645a97…3ca1
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3f44ca72…f571
0x065c9d…c394
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