← previous blocknext block →recent activity
Analyzing
Block #84,359,993
26 transactions · 24 stateful · 2026-06-29 00:52:18 UTC
Parallelism
85/100
Blocked
46%
Avg conflicts / tx
0.88
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,359,993 · 26 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w17w08w111w312w013w115w216w018w319w321w222w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7add284…8d28
0x34b655…2a6f
8 touches
6 conflicts
0x405da3e8…d197
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
6 touches
3 conflicts
0xb6d6d740…e91c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 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: Perpl
6 conflicts on slot 0xd7add284d9…568d28
Audit this contract →
← previous block·next block →recent activity