← previous blocknext block →recent activity
Analyzing
Block #83,615,870
23 transactions · 21 stateful · 2026-06-25 14:11:53 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.57
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,615,870 · 23 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
1w02w13w25w26w37w211w012w113w214w015w318w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x487922c6…dbd2
0x34b655…2a6f
6 touches
3 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x124be23b…2cca
0x34b655…2a6f
6 touches
3 conflicts
0x5d66225b…df5f
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001b
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 0x487922c60c…e4dbd2
Audit this contract →
← previous block·next block →recent activity