← previous blocknext block →recent activity
Analyzing
Block #84,594,520
12 transactions · 11 stateful · 2026-06-30 02:56:21 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,594,520 · 12 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
1w02w13w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5fad6fee…7714
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbe6ea3b9…f592
0xd32edf…ff58
3 touches
1 conflict
0x08711e01…a286
0x065c9d…c394
2 touches
0 conflicts
0x1bff4795…fe88
0x065c9d…c394
2 touches
0 conflicts
0x97713081…0adc
0x065c9d…c394
2 touches
0 conflicts
0xd3913524…54d6
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 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: Perpl
1 conflict on slot 0x5fad6fee64…277714
Audit this contract →
← previous block·next block →recent activity