← previous blocknext block →recent activity
Analyzing
Block #84,500,015
22 transactions · 18 stateful · 2026-06-29 16:25:47 UTC
Parallelism
86/100
Blocked
39%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,500,015 · 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
1w02w13w04w06w07w18w29w010w112w013w117w219w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb067026…9eb8
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x5e215df6…a2d1
0xd32edf…ff58
5 touches
3 conflicts
0x8e739938…e7ab
0x34b655…2a6f
4 touches
1 conflict
0xaa0fd315…db75
0x34b655…2a6f
4 touches
1 conflict
0xb0cc81dc…0fa2
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: 0x69df8a43…506292
3 conflicts on slot 0xdb06702604…0f9eb8
Audit this contract →
← previous block·next block →recent activity