← previous blocknext block →recent activity
Analyzing
Block #83,654,762
17 transactions · 16 stateful · 2026-06-25 18:31:40 UTC
Parallelism
41/100
Blocked
69%
Avg conflicts / tx
2.06
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #83,654,762 · 17 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w59w614w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2c53a187…3646
0x34b655…2a6f
16 touches
28 conflicts
0xe7080c85…e9ba
0x34b655…2a6f
12 touches
15 conflicts
0xc0b9bd73…7f1c
0x34b655…2a6f
10 touches
10 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0x487922c6…dbd2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xa0c6e179…a103
0x34b655…2a6f
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
28 conflicts on slot 0x2c53a187ea…bc3646
Audit this contract →
← previous block·next block →recent activity