← previous blocknext block →recent activity
Analyzing
Block #84,047,651
20 transactions · 15 stateful · 2026-06-27 14:11:32 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,047,651 · 20 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w06w17w210w112w017w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x49194594…2c70
0x34b655…2a6f
6 touches
3 conflicts
0x18f147b8…cfb4
0x34b655…2a6f
4 touches
1 conflict
0x32359294…7113
0x34b655…2a6f
4 touches
1 conflict
0x4e1ce17e…98a7
0x34b655…2a6f
4 touches
1 conflict
0x4ef263bb…fcf0
0x34b655…2a6f
4 touches
1 conflict
0x6db8bfb1…5be2
0x34b655…2a6f
4 touches
1 conflict
0x6dff275f…7bb0
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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity