← previous blocknext block →recent activity
Analyzing
Block #83,655,022
22 transactions · 20 stateful · 2026-06-25 18:33:24 UTC
Parallelism
82/100
Blocked
35%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,655,022 · 22 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
1w02w14w05w113w014w216w318w019w120w321w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6b7c45d…9d5a
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xea2d3331…6e35
0x1b6862…e19c
4 touches
1 conflict
0x47d04781…2b47
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 0xb6b7c45de7…c49d5a
Audit this contract →
← previous block·next block →recent activity