← previous blocknext block →recent activity
Analyzing
Block #85,527,261
37 transactions · 31 stateful · 2026-07-04 10:33:53 UTC
Parallelism
81/100
Blocked
61%
Avg conflicts / tx
1.27
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #85,527,261 · 37 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w07w19w010w311w113w314w415w117w219w420w529w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x04fdea…47d7
12 touches
15 conflicts
0x64f7628d…5238
0xd32edf…ff58
11 touches
15 conflicts
0x9ff176a9…152e
0x065c9d…c394
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0029
0x1b6862…e19c
8 touches
6 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: 0x04fdeac2…f747d7
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity