← previous blocknext block →recent activity
Analyzing
Block #83,969,134
41 transactions · 37 stateful · 2026-06-27 05:28:31 UTC
Parallelism
81/100
Blocked
59%
Avg conflicts / tx
1.68
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,969,134 · 41 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w37w49w510w411w530w331w632w535w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x1be22e30…92fc
0xd32edf…ff58
11 touches
15 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
10 touches
10 conflicts
0x8726ff39…3be8
0x34b655…2a6f
10 touches
10 conflicts
0xe2e45419…f17b
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
10 touches
10 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0x17a7f697…dcb3
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: Perpl
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity