← previous blocknext block →recent activity
Analyzing
Block #83,655,258
16 transactions · 15 stateful · 2026-06-25 18:34:59 UTC
Parallelism
63/100
Blocked
33%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,655,258 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w310w011w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x478e6e08…83bf
0x34b655…2a6f
10 touches
10 conflicts
0x16dce2e7…6f05
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x4f4bdabd…ffba
0x34b655…2a6f
4 touches
1 conflict
0x5f447bf3…57c7
0x34b655…2a6f
4 touches
1 conflict
0x67034933…8f20
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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
10 conflicts on slot 0x478e6e0871…8083bf
Audit this contract →
← previous block·next block →recent activity