← previous blocknext block →recent activity
Analyzing
Block #84,491,719
23 transactions · 20 stateful · 2026-06-29 15:30:25 UTC
Parallelism
83/100
Blocked
45%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,491,719 · 23 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w19w010w114w115w116w217w118w220w221w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8fcf2308…746e
0x34b655…2a6f
6 touches
3 conflicts
0x7b7af531…48f1
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf5970b31…f34c
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x69941f7e…3b1d
0x34b655…2a6f
4 touches
1 conflict
0x80a47aa8…bbf6
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 0x8fcf2308ed…e1746e
Audit this contract →
← previous block·next block →recent activity