← previous blocknext block →recent activity
Analyzing
Block #87,122,613
11 transactions · 10 stateful · 2026-07-11 20:06:39 UTC
Parallelism
82/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,122,613 · 11 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
1w02w14w05w06w17w1
- 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
0xa9a49465…0424
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x33c26dc9…5f12
0x065c9d…c394
2 touches
0 conflicts
0xa4f80979…4d71
0x065c9d…c394
2 touches
0 conflicts
0xa924b64a…7a0b
0x065c9d…c394
2 touches
0 conflicts
0xd35bb5ac…3586
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