← previous blocknext block →recent activity
Analyzing
Block #87,316,922
16 transactions · 15 stateful · 2026-07-12 17:46:33 UTC
Parallelism
88/100
Blocked
20%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,316,922 · 16 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
1w02w16w011w012w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0006
0x0a2fbf…29b1
4 touches
1 conflict
0x4250b098…c708
0x0a2fbf…29b1
4 touches
1 conflict
0x4250b098…c709
0x0a2fbf…29b1
4 touches
1 conflict
0x4250b098…c70c
0x0a2fbf…29b1
4 touches
1 conflict
0x84e048fa…24f7
0x0a2fbf…29b1
4 touches
1 conflict
0x84e048fa…24f8
0x0a2fbf…29b1
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity