← previous blocknext block →recent activity
Analyzing
Block #83,618,137
26 transactions · 22 stateful · 2026-06-25 14:27:03 UTC
Parallelism
73/100
Blocked
50%
Avg conflicts / tx
1.19
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,618,137 · 26 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w36w47w08w19w210w311w412w513w624w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0xda7f9bd2…e332
0x34b655…2a6f
8 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x6dd716c2…97cc
0xd32edf…ff58
7 touches
6 conflicts
0xed863ec8…90d9
0x1b6862…e19c
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity