← previous blocknext block →recent activity
Analyzing
Block #83,628,596
14 transactions · 13 stateful · 2026-06-25 15:36:59 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.86
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,628,596 · 14 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
2w03w04w16w17w28w312w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
8 touches
6 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0x2bc62c2a…0767
0x34b655…2a6f
4 touches
1 conflict
0x5396d712…a139
0x34b655…2a6f
4 touches
1 conflict
0x58f5d121…86ab
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x75291f8b…3ac0
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 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity