← previous blocknext block →recent activity
Analyzing
Block #83,398,517
26 transactions · 20 stateful · 2026-06-24 14:01:20 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
1.42
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,398,517 · 26 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w311w012w113w214w315w417w518w619w721w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x757b0543…e087
0x34b655…2a6f
6 touches
3 conflicts
0x901d9f30…67a4
0x34b655…2a6f
6 touches
3 conflicts
0xec7b070f…db9a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x36d366fe…7adc
0xa6afd3…d132
6 touches
3 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity