← previous blocknext block →recent activity
Analyzing
Block #85,989,749
34 transactions · 24 stateful · 2026-07-06 13:56:03 UTC
Parallelism
85/100
Blocked
42%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,989,749 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w011w119w020w121w222w323w224w025w429w030w131w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0xac55452a…17f6
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf5310ef7…485a
0x40c49f…2af0
6 touches
3 conflicts
0x52e69143…95ad
0x065c9d…c394
6 touches
3 conflicts
0xf8f1e808…a4fd
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity