← previous blocknext block →recent activity
Analyzing
Block #83,629,994
23 transactions · 22 stateful · 2026-06-25 15:46:18 UTC
Parallelism
65/100
Blocked
55%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,629,994 · 23 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w18w09w110w211w312w413w514w615w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x76477ddf…b8f8
0xc8689a…ee79
6 touches
3 conflicts
0x049cca71…b102
0x34b655…2a6f
6 touches
3 conflicts
0x5396d712…a139
0x34b655…2a6f
6 touches
3 conflicts
0x60146498…2704
0x34b655…2a6f
6 touches
3 conflicts
0x6767aeb1…eabc
0x34b655…2a6f
6 touches
3 conflicts
0x785889c9…0603
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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity