← previous blocknext block →recent activity
Analyzing
Block #83,627,860
31 transactions · 19 stateful · 2026-06-25 15:32:03 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,627,860 · 31 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w417w018w120w021w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xf6d99a58…19ae
0xd32edf…ff58
7 touches
6 conflicts
0x8e5cc690…b06b
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x9fbabe09…8dd6
0x34b655…2a6f
6 touches
3 conflicts
0x71632345…6ee9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0x9fa1409b…0e56
0x1b6862…e19c
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity