← previous blocknext block →recent activity
Analyzing
Block #84,039,148
52 transactions · 38 stateful · 2026-06-27 13:14:56 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.35
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #84,039,148 · 52 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w114w215w218w319w020w122w224w325w426w527w643w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
14 touches
21 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002b
0x1b6862…e19c
8 touches
6 conflicts
0x9ac040c1…8222
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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: 0xd637b38f…c64160
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity