← previous blocknext block →recent activity
Analyzing
Block #84,289,529
16 transactions · 9 stateful · 2026-06-28 17:02:39 UTC
Parallelism
81/100
Blocked
33%
Avg conflicts / tx
0.19
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,289,529 · 16 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
1w02w16w27w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x316dba61…9c6d
0xa6afd3…d132
3 touches
1 conflict
0x9851a0b3…1ce6
0x065c9d…c394
2 touches
0 conflicts
0xa7b3b655…fc03
0x065c9d…c394
2 touches
0 conflicts
0xd228aa40…cbee
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity