← previous blocknext block →recent activity
Analyzing
Block #84,364,403
21 transactions · 17 stateful · 2026-06-29 01:21:40 UTC
Parallelism
81/100
Blocked
41%
Avg conflicts / tx
0.48
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,364,403 · 21 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
1w02w04w05w17w210w111w214w115w219w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0x975680c7…0e39
0xa6afd3…d132
6 touches
3 conflicts
0x1951ee47…540f
0x34b655…2a6f
4 touches
1 conflict
0x3817764d…242b
0x34b655…2a6f
4 touches
1 conflict
0x8f0e8a2f…a850
0x34b655…2a6f
4 touches
1 conflict
0x93641233…06f5
0x34b655…2a6f
4 touches
1 conflict
0x98af2a4f…5ec1
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity