← previous blocknext block →recent activity
Analyzing
Block #83,670,394
15 transactions · 14 stateful · 2026-06-25 20:15:54 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,670,394 · 15 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
1w02w14w26w09w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa37d59c6…996b
0x34b655…2a6f
6 touches
3 conflicts
0xb670a63e…ead8
0x34b655…2a6f
6 touches
3 conflicts
0x27d815d2…5ca9
0x34b655…2a6f
4 touches
1 conflict
0x280117c9…f4b6
0x34b655…2a6f
4 touches
1 conflict
0x2fdfa032…139c
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x46cb00b8…6d16
0x34b655…2a6f
4 touches
1 conflict
0x51cd1d5b…24ed
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
3 conflicts on slot 0xa37d59c66f…3f996b
Audit this contract →
← previous block·next block →recent activity