← previous blocknext block →recent activity
Analyzing
Block #87,291,996
15 transactions · 13 stateful · 2026-07-12 14:59:55 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #87,291,996 · 15 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
1w02w13w04w15w09w210w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x61377ba1…0bef
0xa6afd3…d132
4 touches
1 conflict
0xad0c145d…72b3
0xa6afd3…d132
4 touches
1 conflict
0x462c8be7…4f83
0xb1dbf0…c0d3
4 touches
1 conflict
0x5ba51e87…44ee
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ac
0xb1dbf0…c0d3
4 touches
1 conflict
0x8a35acfb…d1ad
0xb1dbf0…c0d3
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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-WETH/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity