← previous blocknext block →recent activity
Analyzing
Block #83,617,122
37 transactions · 28 stateful · 2026-06-25 14:20:16 UTC
Parallelism
78/100
Blocked
54%
Avg conflicts / tx
1.14
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #83,617,122 · 37 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
1w02w13w29w012w113w214w015w116w217w318w419w520w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x8d3f06db…98cb
0x34b655…2a6f
8 touches
6 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
8 touches
6 conflicts
0x75291f8b…3ac0
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
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