← previous blocknext block →recent activity
Analyzing
Block #83,841,192
35 transactions · 34 stateful · 2026-06-26 15:15:33 UTC
Parallelism
80/100
Blocked
62%
Avg conflicts / tx
1.51
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,841,192 · 35 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
1w02w03w14w25w37w08w19w210w311w412w513w619w120w323w425w528w129w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x975680c7…0e39
0xa6afd3…d132
8 touches
6 conflicts
0x3287e4ec…eaa3
0xa6afd3…d132
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xf324b405…ca30
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
21 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity