← previous blocknext block →recent activity
Analyzing
Block #83,660,045
17 transactions · 16 stateful · 2026-06-25 19:06:53 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,660,045 · 17 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
1w02w13w24w05w06w18w210w015w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x79e62da8…efdc
0x34b655…2a6f
8 touches
6 conflicts
0x2fac9bcf…279a
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xac61d3a4…7da8
0x34b655…2a6f
6 touches
3 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0x0ad4dbe8…ae93
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 0x79e62da89b…71efdc
Audit this contract →
← previous block·next block →recent activity