← previous blocknext block →recent activity
Analyzing
Block #83,659,836
16 transactions · 13 stateful · 2026-06-25 19:05:30 UTC
Parallelism
75/100
Blocked
31%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,659,836 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w07w18w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x42341814…60f1
0x34b655…2a6f
8 touches
6 conflicts
0xfbf0b409…2ac6
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0xc0dabdc4…6aab
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x7ee6007b…fd68
0x34b655…2a6f
6 touches
3 conflicts
0x5b72a110…4653
0x34b655…2a6f
4 touches
1 conflict
0x9ddc62d5…6f4c
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 0x423418147b…3460f1
Audit this contract →
← previous block·next block →recent activity