← previous blocknext block →recent activity
Analyzing
Block #84,545,171
12 transactions · 11 stateful · 2026-06-29 21:27:14 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,545,171 · 12 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
2w04w05w19w110w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd624c922…929e
0x065c9d…c394
4 touches
1 conflict
0x4f1a5666…d01d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xf3e71703…f1f1
0x065c9d…c394
3 touches
1 conflict
0x914848ae…9e28
0x065c9d…c394
3 touches
1 conflict
0x9a909b54…ac2c
0x065c9d…c394
3 touches
1 conflict
0x7420f364…f620
0x065c9d…c394
3 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: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity