← previous blocknext block →recent activity
Analyzing
Block #84,618,085
16 transactions · 13 stateful · 2026-06-30 05:33:22 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.63
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,618,085 · 16 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
2w04w05w16w17w08w210w211w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xe75cebb6…6b36
0x065c9d…c394
6 touches
3 conflicts
0x56785e37…a197
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xf1b8c26d…5189
0x34b655…2a6f
4 touches
1 conflict
0x5234b8ba…3bd2
0x065c9d…c394
3 touches
1 conflict
0x09000000…0007
0x000000…1000
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity