← previous blocknext block →recent activity
Analyzing
Block #83,626,192
16 transactions · 15 stateful · 2026-06-25 15:20:53 UTC
Parallelism
63/100
Blocked
40%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,626,192 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w514w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x915c095e…c1e5
0x69df8a…6292
8 touches
6 conflicts
0x8d0d8061…d410
0xc8689a…ee79
8 touches
6 conflicts
0xcfe06a18…b5b5
0x69df8a…6292
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x7a12283f…b18a
0x69df8a…6292
8 touches
6 conflicts
0x00000000…003d
0x851145…3f07
8 touches
6 conflicts
0xd8fd2add…50fc
0x69df8a…6292
8 touches
6 conflicts
0x250c3574…21db
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: 0x69df8a43…506292
6 conflicts on slot 0x915c095e9c…c3c1e5
Audit this contract →
← previous block·next block →recent activity