← previous blocknext block →recent activity
Analyzing
Block #83,453,535
41 transactions · 28 stateful · 2026-06-24 20:08:55 UTC
Parallelism
63/100
Blocked
71%
Avg conflicts / tx
3
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #83,453,535 · 41 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w19w012w114w215w320w021w122w223w324w425w526w627w728w829w930w1031w1132w1233w1334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xee7978e9…2869
0x34b655…2a6f
14 touches
21 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0xdf37a93d…879b
0x34b655…2a6f
12 touches
15 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
10 touches
10 conflicts
0x3da49e5d…8067
0x34b655…2a6f
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity