← previous blocknext block →recent activity
Analyzing
Block #84,460,416
28 transactions · 23 stateful · 2026-06-29 12:01:32 UTC
Parallelism
79/100
Blocked
35%
Avg conflicts / tx
0.39
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,460,416 · 28 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
5w07w19w011w112w213w317w018w019w120w125w426w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7dc64b2c…05e7
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x892eedd0…bf40
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc94da5de…7ca7
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 0x7dc64b2c34…6405e7
Audit this contract →
← previous block·next block →recent activity