← previous blocknext block →recent activity
Analyzing
Block #88,340,057
14 transactions · 12 stateful · 2026-07-17 11:50:59 UTC
Parallelism
86/100
Blocked
8%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,340,057 · 14 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x160f117d…8e90
0x065c9d…c394
4 touches
1 conflict
0xc67beecf…25f6
0x065c9d…c394
3 touches
1 conflict
0x3ee0e8dc…2d41
0x065c9d…c394
3 touches
1 conflict
0x54d985f9…ff9e
0x065c9d…c394
3 touches
1 conflict
0x7dda0430…be00
0x065c9d…c394
2 touches
0 conflicts
0xf16a3337…95e9
0x065c9d…c394
2 touches
0 conflicts
0xf4c67525…106e
0x065c9d…c394
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