← previous blocknext block →recent activity
Analyzing
Block #83,628,228
58 transactions · 43 stateful · 2026-06-25 15:34:31 UTC
Parallelism
69/100
Blocked
72%
Avg conflicts / tx
3.34
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #83,628,228 · 58 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w112w215w317w419w020w121w223w327w028w129w230w331w432w533w634w735w846w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
36 touches
153 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
14 touches
21 conflicts
0xe02484a6…c32e
0xc8689a…ee79
14 touches
21 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
14 touches
21 conflicts
0x37a276a3…673f
0x34b655…2a6f
14 touches
21 conflicts
0x5fad6fee…7714
0x34b655…2a6f
12 touches
15 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 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
153 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity