← previous blocknext block →recent activity
Analyzing
Block #83,654,397
15 transactions · 15 stateful · 2026-06-25 18:29:16 UTC
Parallelism
53/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,654,397 · 15 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
1w04w15w28w29w311w312w413w514w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x705f195d…cc32
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x6ac6d1bf…8b19
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x4bdcc5ee…7e90
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
6 conflicts on slot 0x705f195df0…e4cc32
Audit this contract →
← previous block·next block →recent activity