← previous blocknext block →recent activity
Analyzing
Block #83,758,102
40 transactions · 35 stateful · 2026-06-26 06:01:01 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
1.5
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,758,102 · 40 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
1w03w05w07w18w29w310w412w122w525w127w328w333w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x58c659ec…3c6c
0x34b655…2a6f
6 touches
3 conflicts
0x5941ac48…c525
0x34b655…2a6f
6 touches
3 conflicts
0x6ebd33e0…a9de
0x34b655…2a6f
6 touches
3 conflicts
0x7506443a…4820
0x34b655…2a6f
6 touches
3 conflicts
0xbc9aaf19…8cfd
0x34b655…2a6f
6 touches
3 conflicts
0xcef70a96…db44
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity