← previous blocknext block →recent activity
Analyzing
Block #83,653,371
15 transactions · 14 stateful · 2026-06-25 18:22:27 UTC
Parallelism
67/100
Blocked
43%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,653,371 · 15 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
1w02w14w05w17w28w310w011w114w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd026fe03…7748
0x34b655…2a6f
10 touches
10 conflicts
0x925c118c…a1d8
0x34b655…2a6f
6 touches
3 conflicts
0xbd2de3e0…4287
0x34b655…2a6f
6 touches
3 conflicts
0xf324b405…ca30
0x34b655…2a6f
6 touches
3 conflicts
0x141c05d6…3976
0x34b655…2a6f
4 touches
1 conflict
0x1af777a9…b403
0x34b655…2a6f
4 touches
1 conflict
0x4c8b47b1…ea57
0x34b655…2a6f
4 touches
1 conflict
0x4fbf296b…b9ea
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 0xd026fe0331…887748
Audit this contract →
← previous block·next block →recent activity