← previous blocknext block →recent activity
Analyzing
Block #83,482,210
15 transactions · 13 stateful · 2026-06-24 23:20:17 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,482,210 · 15 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
6w07w18w29w012w013w114w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0x85ac0ab8…a3d8
0x34b655…2a6f
6 touches
3 conflicts
0x040af16d…1030
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
4 touches
1 conflict
0x604d1daf…bf48
0x34b655…2a6f
4 touches
1 conflict
0x82dd2252…e1ce
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
3 conflicts on slot 0xc0b9bd73c8…277f1c
Audit this contract →
← previous block·next block →recent activity