← previous blocknext block →recent activity
Analyzing
Block #84,250,385
32 transactions · 24 stateful · 2026-06-28 12:41:54 UTC
Parallelism
81/100
Blocked
63%
Avg conflicts / tx
1.09
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,250,385 · 32 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w39w412w013w114w215w319w020w121w222w023w127w129w330w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x6d36509f…3ba9
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x0a85a226…83c1
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
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: Perpl
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity