← previous blocknext block →recent activity
Analyzing
Block #83,629,600
26 transactions · 25 stateful · 2026-06-25 15:43:41 UTC
Parallelism
77/100
Blocked
28%
Avg conflicts / tx
0.58
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,629,600 · 26 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
7w08w19w212w013w114w215w324w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90fefe5e…f0c6
0x34b655…2a6f
10 touches
10 conflicts
0x5396d712…a139
0x34b655…2a6f
8 touches
6 conflicts
0x82dd2252…e1ce
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
8 touches
6 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x09fdab51…0f1e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xaa7ee7…f0e4
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
10 conflicts on slot 0x90fefe5e59…bbf0c6
Audit this contract →
← previous block·next block →recent activity