← previous blocknext block →recent activity
Analyzing
Block #84,021,429
17 transactions · 14 stateful · 2026-06-27 11:16:57 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,021,429 · 17 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w19w010w112w013w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc51e21c5…5391
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x7301308d…168a
0x065c9d…c394
4 touches
1 conflict
0xe7992c5e…41b9
0xd32edf…ff58
3 touches
1 conflict
0xa8c84848…24d1
0x5afd3e…7620
2 touches
0 conflicts
0x00000000…0006
0x60bb42…87ea
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0xc51e21c5c6…cc5391
Audit this contract →
← previous block·next block →recent activity