← previous blocknext block →recent activity
Analyzing
Block #83,653,074
14 transactions · 13 stateful · 2026-06-25 18:20:28 UTC
Parallelism
43/100
Blocked
62%
Avg conflicts / tx
1.21
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,653,074 · 14 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w49w111w512w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37baeabc…8175
0x34b655…2a6f
8 touches
6 conflicts
0x4467ecee…e95b
0x34b655…2a6f
8 touches
6 conflicts
0x5f447bf3…57c7
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x1af777a9…b403
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0x37baeabca3…7b8175
Audit this contract →
← previous block·next block →recent activity