← previous blocknext block →recent activity
Analyzing
Block #86,056,221
17 transactions · 14 stateful · 2026-07-06 21:20:06 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,056,221 · 17 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
6w010w011w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95523e2a…4c01
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x3be36b7d…dce5
0x065c9d…c394
3 touches
1 conflict
0x7b0e6611…bf79
0x754704…b603
2 touches
0 conflicts
0x00000000…000a
0xa45723…b4c0
2 touches
0 conflicts
0x1790ae69…c5ac
0xc4c20e…b2db
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 0x95523e2aaf…734c01
Audit this contract →
← previous block·next block →recent activity