← previous blocknext block →recent activity
Analyzing
Block #84,563,546
11 transactions · 10 stateful · 2026-06-29 23:29:55 UTC
Parallelism
64/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,563,546 · 11 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
5w06w19w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x02c4bb0f…f2c8
0x34b655…2a6f
6 touches
3 conflicts
0x74888025…a5b8
0x34b655…2a6f
6 touches
3 conflicts
0x1d7fc974…1dad
0x34b655…2a6f
4 touches
1 conflict
0x21bdd116…c237
0x34b655…2a6f
4 touches
1 conflict
0x2c15adb7…e65d
0x34b655…2a6f
4 touches
1 conflict
0x374fc18a…6998
0x34b655…2a6f
4 touches
1 conflict
0x3f75fb9e…0d2e
0x34b655…2a6f
4 touches
1 conflict
0x43805d18…14ca
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 0x02c4bb0f0a…d0f2c8
Audit this contract →
← previous block·next block →recent activity