← previous blocknext block →recent activity
Analyzing
Block #84,045,748
9 transactions · 7 stateful · 2026-06-27 13:58:55 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,045,748 · 9 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae8d26ce…f2cd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1328d6c5…77ca
0x065c9d…c394
4 touches
1 conflict
0x3d1e5f59…fd1a
0x065c9d…c394
3 touches
1 conflict
0x497f04be…b876
0x065c9d…c394
3 touches
1 conflict
0xa0b6a2f6…e545
0x065c9d…c394
3 touches
1 conflict
0x09106a95…1467
0x33176b…e078
2 touches
0 conflicts
0xdbadf6b0…43b2
0x33176b…e078
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 0xae8d26cea6…70f2cd
Audit this contract →
← previous block·next block →recent activity