← previous blocknext block →recent activity
Analyzing
Block #83,653,616
20 transactions · 17 stateful · 2026-06-25 18:24:05 UTC
Parallelism
70/100
Blocked
41%
Avg conflicts / tx
0.75
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,653,616 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w412w213w417w018w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdb7c435f…f490
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0x022f72c3…07b6
0xc8689a…ee79
6 touches
3 conflicts
0x704db324…e324
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdd58acd9…fbf0
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
10 conflicts on slot 0xdb7c435f8d…b5f490
Audit this contract →
← previous block·next block →recent activity