← previous blocknext block →recent activity
Analyzing
Block #83,616,660
45 transactions · 33 stateful · 2026-06-25 14:17:10 UTC
Parallelism
64/100
Blocked
70%
Avg conflicts / tx
2.2
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #83,616,660 · 45 txs across 16 waves · depth 16
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w07w18w011w313w420w221w324w025w126w227w328w429w530w631w732w833w934w1035w1143w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x487922c6…dbd2
0x34b655…2a6f
8 touches
6 conflicts
0x53deb74e…24b4
0x34b655…2a6f
8 touches
6 conflicts
0x59d2aa91…a39a
0x34b655…2a6f
8 touches
6 conflicts
0x7485bb0e…d1e0
0x34b655…2a6f
8 touches
6 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity