← previous blocknext block →recent activity
Analyzing
Block #85,012,090
22 transactions · 19 stateful · 2026-07-02 01:19:25 UTC
Parallelism
86/100
Blocked
37%
Avg conflicts / tx
0.45
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,012,090 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w08w110w011w112w213w114w220w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2f7f1a44…eeeb
0x34b655…2a6f
6 touches
3 conflicts
0x5bdb0bbb…f5a2
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x424eca3b…f2ab
0xa6afd3…d132
4 touches
1 conflict
0xdc120748…ff36
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x731e6d82…2883
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
3 conflicts on slot 0x2f7f1a44b5…3beeeb
Audit this contract →
← previous block·next block →recent activity