← previous blocknext block →recent activity
Analyzing
Block #83,637,669
25 transactions · 23 stateful · 2026-06-25 16:37:37 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,637,669 · 25 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
1w02w14w05w16w07w08w29w314w115w219w122w023w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x75cdffd8…c217
0x34b655…2a6f
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x0213af2e…926e
0x34b655…2a6f
4 touches
1 conflict
0x0faf7d44…c1cb
0x34b655…2a6f
4 touches
1 conflict
0x1f495928…7b11
0x34b655…2a6f
4 touches
1 conflict
0x30c5329c…711c
0x34b655…2a6f
4 touches
1 conflict
0x40cd0940…ff35
0x34b655…2a6f
4 touches
1 conflict
0x826cce18…251c
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
10 conflicts on slot 0x75cdffd8c9…dec217
Audit this contract →
← previous block·next block →recent activity