← previous blocknext block →recent activity
Analyzing
Block #84,547,672
20 transactions · 19 stateful · 2026-06-29 21:44:09 UTC
Parallelism
80/100
Blocked
37%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,547,672 · 20 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
2w03w18w09w110w212w214w316w017w318w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x7b9a42f7…7b88
0xa6afd3…d132
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe1593d74…b99c
0x34b655…2a6f
4 touches
1 conflict
0x40970e69…da50
0x69df8a…6292
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: Kuru Exchange: MarginAccount
3 conflicts on slot 0xef65bff33c…857c9d
Audit this contract →
← previous block·next block →recent activity