← previous blocknext block →recent activity
Analyzing
Block #84,462,160
25 transactions · 22 stateful · 2026-06-29 12:13:13 UTC
Parallelism
76/100
Blocked
41%
Avg conflicts / tx
0.72
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,462,160 · 25 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
5w06w18w210w011w113w214w316w017w419w120w523w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49194594…2c70
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x8437a898…4e18
0x34b655…2a6f
6 touches
3 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
6 touches
3 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
6 touches
3 conflicts
0x921a58d1…db22
0x34b655…2a6f
4 touches
1 conflict
0x005ee556…db47
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 0x4919459402…d42c70
Audit this contract →
← previous block·next block →recent activity