← previous blocknext block →recent activity
Analyzing
Block #83,652,770
19 transactions · 16 stateful · 2026-06-25 18:18:26 UTC
Parallelism
58/100
Blocked
50%
Avg conflicts / tx
1.63
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,652,770 · 19 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
2w03w14w25w36w47w512w216w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc9fe0433…7f01
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0x73ca2093…8dd6
0x34b655…2a6f
8 touches
6 conflicts
0xbbb9fa77…d121
0x34b655…2a6f
8 touches
6 conflicts
0xc34f7ec0…59cd
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xac45920c…a54b
0x34b655…2a6f
6 touches
3 conflicts
0x5bd818fc…4f86
0x34b655…2a6f
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 0xc9fe0433ca…417f01
Audit this contract →
← previous block·next block →recent activity