← previous blocknext block →recent activity
Analyzing
Block #83,845,412
78 transactions · 66 stateful · 2026-06-26 15:43:45 UTC
Parallelism
76/100
Blocked
76%
Avg conflicts / tx
3.81
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,845,412 · 78 txs across 19 waves · depth 19
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w516w117w219w420w521w623w724w826w927w728w1029w1168w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
38 touches
171 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
20 touches
45 conflicts
0x7a175517…d343
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0x14d1bf0e…e0a0
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x52e94a40…c51a
0x34b655…2a6f
14 touches
21 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
171 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity