← previous blocknext block →recent activity
Analyzing
Block #85,216,108
25 transactions · 24 stateful · 2026-07-03 00:01:44 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
2.04
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #85,216,108 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
20 touches
45 conflicts
0x00000000…000a
0x90c374…be45
20 touches
45 conflicts
0x731e6d82…2883
0x065c9d…c394
4 touches
1 conflict
0x987aeb55…0e2a
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x126a0344…4465
0x34b655…2a6f
4 touches
1 conflict
0x58603063…4ef0
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: 0x90c3747c…0ebe45
45 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity