← previous blocknext block →recent activity
Analyzing
Block #84,040,141
34 transactions · 30 stateful · 2026-06-27 13:21:35 UTC
Parallelism
85/100
Blocked
50%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,040,141 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w48w011w112w013w114w216w118w019w120w225w327w128w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe560375e…4626
0x34b655…2a6f
10 touches
10 conflicts
0x3af0dd8e…0024
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x61862dc5…2511
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
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
10 conflicts on slot 0xe560375e1e…614626
Audit this contract →
← previous block·next block →recent activity