← previous blocknext block →recent activity
Analyzing
Block #83,843,466
40 transactions · 38 stateful · 2026-06-26 15:30:45 UTC
Parallelism
73/100
Blocked
76%
Avg conflicts / tx
2.48
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #83,843,466 · 40 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w08w39w410w517w129w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0x402dbdd4…734f
0xd32edf…ff58
11 touches
15 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x5c3cb0f1…a9fa
0x34b655…2a6f
10 touches
10 conflicts
0x78694995…f66e
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xe27b0bdf…b21a
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
36 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity