← previous blocknext block →recent activity
Analyzing
Block #83,842,929
38 transactions · 33 stateful · 2026-06-26 15:27:10 UTC
Parallelism
76/100
Blocked
64%
Avg conflicts / tx
1.92
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,842,929 · 38 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w27w38w413w026w327w531w432w533w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
12 touches
15 conflicts
0x3f0a8d1c…53c2
0xd32edf…ff58
11 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x9dbefc67…4855
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity