← previous blocknext block →recent activity
Analyzing
Block #86,955,191
16 transactions · 16 stateful · 2026-07-11 01:28:12 UTC
Parallelism
88/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,955,191 · 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
1w08w09w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52e69143…95ad
0x065c9d…c394
4 touches
1 conflict
0xb7b1a9a4…0c7e
0x34b655…2a6f
4 touches
1 conflict
0xb7b1a9a4…0c7f
0x34b655…2a6f
4 touches
1 conflict
0x58aaa1f9…008d
0x065c9d…c394
4 touches
1 conflict
0xd69bec2a…118e
0x34b655…2a6f
4 touches
1 conflict
0xeaed2cda…78bb
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0713e618…8e67
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-MON/USDC
1 conflict on slot 0x52e6914362…6e95ad
Audit this contract →
← previous block·next block →recent activity