← previous blocknext block →recent activity
Analyzing
Block #74,442,397
8 transactions · 7 stateful · 2026-05-14 02:00:55 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,442,397 · 8 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
0x10911bbe…a2a4
0x065c9d…c394
4 touches
1 conflict
0x5e1cad50…c1bc
0x065c9d…c394
3 touches
1 conflict
0x113b3a26…4a92
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0000
0x1bcd3c…c460
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0xfb083229…0138
0x2a68ba…90c5
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 0x10911bbeb4…eda2a4
Audit this contract →
← previous block·next block →recent activity