← previous blocknext block →recent activity
Analyzing
Block #83,452,563
22 transactions · 17 stateful · 2026-06-24 20:02:24 UTC
Parallelism
82/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,452,563 · 22 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
1w02w13w25w06w111w313w014w116w118w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb30e1191…9e3c
0x34b655…2a6f
8 touches
6 conflicts
0x877a5aff…d908
0xd32edf…ff58
7 touches
6 conflicts
0x1222e42d…7dc8
0x34b655…2a6f
4 touches
1 conflict
0x1afc718b…765b
0x34b655…2a6f
4 touches
1 conflict
0x2484cc15…5afc
0x34b655…2a6f
4 touches
1 conflict
0x38ec2c24…ef42
0x34b655…2a6f
4 touches
1 conflict
0x402eeda0…a425
0x34b655…2a6f
4 touches
1 conflict
0x7dacf213…bbf7
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 0xb30e119129…4f9e3c
Audit this contract →
← previous block·next block →recent activity