← previous blocknext block →recent activity
Analyzing
Block #83,410,485
34 transactions · 30 stateful · 2026-06-24 15:21:22 UTC
Parallelism
79/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,410,485 · 34 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w26w17w29w311w012w114w015w116w219w320w421w522w624w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0xec7b070f…db9a
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x757b0543…e087
0x34b655…2a6f
8 touches
6 conflicts
0xb6b9800d…0682
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x36d366fe…7adc
0xa6afd3…d132
8 touches
6 conflicts
0x9cf5ac50…1be9
0xa6afd3…d132
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