← previous blocknext block →recent activity
Analyzing
Block #83,578,508
17 transactions · 14 stateful · 2026-06-25 10:02:26 UTC
Parallelism
65/100
Blocked
36%
Avg conflicts / tx
0.88
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,578,508 · 17 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
3w04w15w26w37w48w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x157dbfb2…4089
0x34b655…2a6f
12 touches
15 conflicts
0xe64e6363…e676
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x864353d4…dcb7
0x34b655…2a6f
12 touches
15 conflicts
0x42f1ead4…72db
0x34b655…2a6f
10 touches
10 conflicts
0x30b27670…4d86
0x34b655…2a6f
8 touches
6 conflicts
0x556440eb…4645
0x34b655…2a6f
4 touches
1 conflict
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
15 conflicts on slot 0x157dbfb216…8d4089
Audit this contract →
← previous block·next block →recent activity