← previous blocknext block →recent activity
Analyzing
Block #87,716,340
16 transactions · 14 stateful · 2026-07-14 14:18:33 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #87,716,340 · 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
3w07w08w09w111w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0733be30…112f
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x93b6fab0…09d6
0x34b655…2a6f
4 touches
1 conflict
0xaedc3dd6…3c3b
0x34b655…2a6f
4 touches
1 conflict
0xdd36917c…b88b
0x34b655…2a6f
4 touches
1 conflict
0x18c702f8…a14d
0x34b655…2a6f
2 touches
0 conflicts
0x211d520a…bf67
0x34b655…2a6f
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