← previous blocknext block →recent activity
Analyzing
Block #83,630,502
19 transactions · 18 stateful · 2026-06-25 15:49:41 UTC
Parallelism
74/100
Blocked
39%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,630,502 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w29w010w111w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x92793b0e…b68e
0x34b655…2a6f
6 touches
3 conflicts
0x9ca0e24b…358d
0xd32edf…ff58
5 touches
3 conflicts
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x23c5c9ed…69bb
0x34b655…2a6f
4 touches
1 conflict
0x2cb897e4…21ea
0x34b655…2a6f
4 touches
1 conflict
0x33a8ac89…1e78
0x34b655…2a6f
4 touches
1 conflict
0x52a0e295…8847
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
3 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity