← previous blocknext block →recent activity
Analyzing
Block #87,304,359
21 transactions · 18 stateful · 2026-07-12 16:22:32 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,304,359 · 21 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
1w010w013w114w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x10dd623d…7304
0x065c9d…c394
2 touches
0 conflicts
0x227dec38…df1f
0x065c9d…c394
2 touches
0 conflicts
0x6714395e…e133
0x065c9d…c394
2 touches
0 conflicts
0x7d0a4f78…4fa1
0x065c9d…c394
2 touches
0 conflicts
0xcc300f02…527f
0x065c9d…c394
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