← previous blocknext block →recent activity
Analyzing
Block #83,633,276
38 transactions · 23 stateful · 2026-06-25 16:08:14 UTC
Parallelism
84/100
Blocked
48%
Avg conflicts / tx
0.5
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,633,276 · 38 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
1w02w13w24w315w121w022w123w024w125w226w329w031w134w435w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x8a8694cb…63f4
0xd32edf…ff58
7 touches
6 conflicts
0xe334a6b5…173c
0x34b655…2a6f
6 touches
3 conflicts
0x6767aeb1…eabc
0x34b655…2a6f
4 touches
1 conflict
0x68496289…ddf6
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xf06c2cf5…61bd
0x34b655…2a6f
4 touches
1 conflict
0xf324b405…ca30
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
6 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity