← previous blocknext block →recent activity
Analyzing
Block #84,248,628
16 transactions · 12 stateful · 2026-06-28 12:30:11 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,248,628 · 16 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
1w05w16w08w19w010w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4a239fe…6918
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0xfa864cf1…a1e5
0xd32edf…ff58
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x09beabbc…065c
0x188d58…ea8e
2 touches
0 conflicts
0x4dd1db39…a994
0x188d58…ea8e
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 0xb4a239fe40…b56918
Audit this contract →
← previous block·next block →recent activity