← previous blocknext block →recent activity
Analyzing
Block #87,348,632
24 transactions · 23 stateful · 2026-07-12 21:18:36 UTC
Parallelism
83/100
Blocked
43%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #87,348,632 · 24 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w07w110w011w012w113w114w216w217w018w321w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0xad0c145d…72b3
0xa6afd3…d132
8 touches
6 conflicts
0x2f93a9d2…dd6d
0x34b655…2a6f
6 touches
3 conflicts
0x6e1cd42e…1f23
0x34b655…2a6f
6 touches
3 conflicts
0x61377ba1…0bef
0xa6afd3…d132
6 touches
3 conflicts
0x3ef0952c…762d
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity