← previous blocknext block →recent activity
Analyzing
Block #83,581,258
35 transactions · 32 stateful · 2026-06-25 10:20:47 UTC
Parallelism
80/100
Blocked
47%
Avg conflicts / tx
1.09
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,581,258 · 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
1w03w04w18w09w111w212w316w017w118w219w320w421w524w125w226w328w532w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xb6b9800d…0682
0x34b655…2a6f
10 touches
10 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x19ce481d…6c36
0x34b655…2a6f
8 touches
6 conflicts
0x7531e9d9…196d
0xa6afd3…d132
8 touches
6 conflicts
0xaa8b5e65…f72a
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
15 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity