← previous blocknext block →recent activity
Analyzing
Block #83,626,403
45 transactions · 37 stateful · 2026-06-25 15:22:18 UTC
Parallelism
71/100
Blocked
57%
Avg conflicts / tx
2.16
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,626,403 · 45 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w18w19w213w014w118w019w120w021w122w223w324w425w526w627w728w829w931w1032w1133w1235w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
26 touches
78 conflicts
0x015374d1…dca3
0x34b655…2a6f
13 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
12 touches
15 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
12 touches
15 conflicts
0x47b1a55b…cfc0
0x34b655…2a6f
10 touches
10 conflicts
0xeb98995b…c0db
0x34b655…2a6f
8 touches
6 conflicts
0xff4ee2c4…6e5e
0x34b655…2a6f
6 touches
3 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
78 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity