← previous blocknext block →recent activity
Analyzing
Block #84,460,987
25 transactions · 22 stateful · 2026-06-29 12:05:22 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,460,987 · 25 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
2w04w06w07w18w111w012w113w214w117w120w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93d680fb…ac21
0x34b655…2a6f
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x2d5c395b…6b5a
0xa6afd3…d132
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x16d612ce…a346
0x34b655…2a6f
4 touches
1 conflict
0x1ebe7da9…e7c5
0x34b655…2a6f
4 touches
1 conflict
0xb3975d93…b4a2
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 0x93d680fb3b…fdac21
Audit this contract →
← previous block·next block →recent activity