← previous blocknext block →recent activity
Analyzing
Block #87,707,140
34 transactions · 25 stateful · 2026-07-14 13:16:53 UTC
Parallelism
82/100
Blocked
36%
Avg conflicts / tx
0.44
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #87,707,140 · 34 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w09w210w312w113w117w021w126w328w029w430w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x92d610a6…9a40
0x2a68ba…90c5
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x2757bcf8…919e
0x065c9d…c394
5 touches
3 conflicts
0x3723c17c…1f12
0xd32edf…ff58
5 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x40e2d65d…2a35
0x3bd359…433a
4 touches
1 conflict
0xce827910…ff22
0x065c9d…c394
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