← previous blocknext block →recent activity
Analyzing
Block #83,625,168
21 transactions · 16 stateful · 2026-06-25 15:14:04 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,625,168 · 21 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w111w012w115w016w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x015374d1…dca3
0x34b655…2a6f
6 touches
3 conflicts
0xd4b70e63…8718
0x34b655…2a6f
6 touches
3 conflicts
0xdf9957df…8d42
0x34b655…2a6f
6 touches
3 conflicts
0x8e4fdba3…18f1
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xac79a0c7…be12
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
3 conflicts on slot 0x015374d181…9fdca3
Audit this contract →
← previous block·next block →recent activity