← previous blocknext block →recent activity
Analyzing
Block #83,655,499
15 transactions · 13 stateful · 2026-06-25 18:36:35 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,655,499 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w08w19w210w111w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa0c6e179…a103
0x34b655…2a6f
6 touches
3 conflicts
0x022f72c3…07b6
0xc8689a…ee79
4 touches
1 conflict
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdba23000…3d7e
0x34b655…2a6f
4 touches
1 conflict
0xe2ebed66…8be2
0x34b655…2a6f
4 touches
1 conflict
0xe46a9e83…22b5
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
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 0xa0c6e1796c…01a103
Audit this contract →
← previous block·next block →recent activity