← previous blocknext block →recent activity
Analyzing
Block #74,636,190
10 transactions · 9 stateful · 2026-05-14 23:38:38 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,636,190 · 10 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab0e95ca…9699
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3ba7a5cc…904d
0x065c9d…c394
3 touches
1 conflict
0x4f44f2d1…5327
0x065c9d…c394
3 touches
1 conflict
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x5ff611d5…b6cd
0x065c9d…c394
2 touches
0 conflicts
0x8bb1e436…aed4
0x065c9d…c394
2 touches
0 conflicts
0xc90d0183…ffe7
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 0xab0e95ca09…7d9699
Audit this contract →
← previous block·next block →recent activity