← previous blocknext block →recent activity
Analyzing
Block #95,556,087
18 transactions · 13 stateful · 2026-08-13 06:10:26 UTC
Parallelism
89/100
Blocked
8%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,556,087 · 18 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
1w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4be46c6c…37b5
0x065c9d…c394
4 touches
1 conflict
0x65720254…ee01
0x065c9d…c394
3 touches
1 conflict
0x01d368df…1674
0x065c9d…c394
3 touches
1 conflict
0x5edfe3f2…3b69
0x065c9d…c394
2 touches
0 conflicts
0xb33ff823…1188
0x065c9d…c394
2 touches
0 conflicts
0xe7d66ddb…7b91
0x065c9d…c394
2 touches
0 conflicts
0xf74be923…9c0a
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