← previous blocknext block →recent activity
Analyzing
Block #84,528,237
14 transactions · 11 stateful · 2026-06-29 19:33:59 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,528,237 · 14 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
1w02w19w210w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52ed5ebf…030a
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x10aab56d…90c9
0x065c9d…c394
4 touches
1 conflict
0x28511565…7499
0x065c9d…c394
4 touches
1 conflict
0xf1a28f04…6d2b
0x065c9d…c394
3 touches
1 conflict
0x7ae6f560…188a
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
1 conflict on slot 0x52ed5ebf01…8c030a
Audit this contract →
← previous block·next block →recent activity