← previous blocknext block →recent activity
Analyzing
Block #83,453,153
53 transactions · 45 stateful · 2026-06-24 20:06:21 UTC
Parallelism
57/100
Blocked
78%
Avg conflicts / tx
4.15
Longest chain
23 deep
Execution timeline
did this block parallelize well?
view
block #83,453,153 · 53 txs across 23 waves · depth 23
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
wave w19
wave w20
wave w21
wave w22
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w410w511w612w713w815w221w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
20 touches
45 conflicts
0x9b6da653…6665
0xd32edf…ff58
17 touches
36 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 conflicts
0xe6950848…9ff6
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0xde53ca4f…19e9
0x34b655…2a6f
14 touches
21 conflicts
0x0876b6b8…98a5
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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity