← previous blocknext block →recent activity
Analyzing
Block #84,493,541
19 transactions · 16 stateful · 2026-06-29 15:42:36 UTC
Parallelism
84/100
Blocked
19%
Avg conflicts / tx
0.16
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,493,541 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w112w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68eef65a…a86d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xec85756f…0ba2
0x34b655…2a6f
4 touches
1 conflict
0xdfc5f346…7b42
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xa6c9a33e…d839
0x34b655…2a6f
4 touches
1 conflict
0x6abc13bb…bfde
0x40c49f…2af0
3 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
2 touches
0 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
1 conflict on slot 0x68eef65a1c…99a86d
Audit this contract →
← previous block·next block →recent activity