← previous blocknext block →recent activity
Analyzing
Block #83,626,466
26 transactions · 21 stateful · 2026-06-25 15:22:43 UTC
Parallelism
81/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,626,466 · 26 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w08w113w014w115w216w318w019w424w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x8d0d8061…d410
0xc8689a…ee79
6 touches
3 conflicts
0x7a12283f…b18a
0x69df8a…6292
6 touches
3 conflicts
0x915c095e…c1e5
0x69df8a…6292
6 touches
3 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
6 touches
3 conflicts
0xd8fd2add…50fc
0x69df8a…6292
6 touches
3 conflicts
0x00000000…003d
0x851145…3f07
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity