← previous blocknext block →recent activity
Analyzing
Block #83,616,966
25 transactions · 24 stateful · 2026-06-25 14:19:13 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
1.8
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,616,966 · 25 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w16w27w38w410w511w621w522w623w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xffc2f21e…b393
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0003
0x019883…2a9a
8 touches
6 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
8 touches
6 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
8 touches
6 conflicts
0x487922c6…dbd2
0x34b655…2a6f
8 touches
6 conflicts
0x69813bdd…c3a0
0x34b655…2a6f
8 touches
6 conflicts
0x9c4bf061…1101
0x34b655…2a6f
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity