← previous blocknext block →recent activity
Analyzing
Block #87,341,066
11 transactions · 10 stateful · 2026-07-12 20:28:01 UTC
Parallelism
82/100
Blocked
40%
Avg conflicts / tx
0.45
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,341,066 · 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
1w02w13w05w06w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x64aaadbf…f9f3
0x34b655…2a6f
4 touches
1 conflict
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x2b335e96…7fa9
0x065c9d…c394
2 touches
0 conflicts
0x2f80a05c…b3db
0x065c9d…c394
2 touches
0 conflicts
0x6fb93949…cea1
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