← previous blocknext block →recent activity
Analyzing
Block #84,524,694
30 transactions · 23 stateful · 2026-06-29 19:10:24 UTC
Parallelism
80/100
Blocked
52%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,524,694 · 30 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
1w02w03w14w26w316w117w018w119w220w321w422w524w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ff2b017…3fa2
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xe02484a6…c32e
0xc8689a…ee79
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x0d2e1791…c1dd
0x34b655…2a6f
8 touches
6 conflicts
0xf64a547c…30f6
0x34b655…2a6f
8 touches
6 conflicts
0x78c30df4…c54d
0xa6afd3…d132
8 touches
6 conflicts
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 0x9ff2b0179a…1c3fa2
Audit this contract →
← previous block·next block →recent activity