← previous blocknext block →recent activity
Analyzing
Block #85,221,153
16 transactions · 15 stateful · 2026-07-03 00:35:20 UTC
Parallelism
63/100
Blocked
67%
Avg conflicts / tx
1.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,221,153 · 16 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
1w02w13w24w35w46w09w111w112w213w314w415w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…000b
0x90c374…be45
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…000a
0x90c374…be45
10 touches
10 conflicts
0x47d4745e…02bb
0x336ed4…c59c
8 touches
6 conflicts
0x10a2bd5d…ad6d
0x8d1565…6723
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xd63e616b…a07d
0x34b655…2a6f
6 touches
3 conflicts
0xd4b0bafb…80ac
0x34b655…2a6f
5 touches
3 conflicts
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
10 conflicts on slot 0x0000000000…00000b
Audit this contract →
← previous block·next block →recent activity