← previous blocknext block →recent activity
Analyzing
Block #83,633,404
51 transactions · 50 stateful · 2026-06-25 16:09:06 UTC
Parallelism
67/100
Blocked
70%
Avg conflicts / tx
4.71
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,633,404 · 51 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w15w26w37w48w59w610w711w812w913w1014w1115w1216w1319w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
34 touches
136 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
28 touches
91 conflicts
0x6ebd33e0…a9de
0x34b655…2a6f
16 touches
28 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
16 touches
28 conflicts
0xb3975d93…b4a2
0x34b655…2a6f
16 touches
28 conflicts
0xd79c9727…1233
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
16 touches
28 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
136 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity