← previous blocknext block →recent activity
Analyzing
Block #87,305,515
16 transactions · 15 stateful · 2026-07-12 16:30:16 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,305,515 · 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
5w07w08w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x14fe1598…d0ba
0x34b655…2a6f
2 touches
0 conflicts
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x588380ee…0a5c
0x34b655…2a6f
2 touches
0 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
0x34b655…2a6f
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