← previous blocknext block →recent activity
Analyzing
Block #74,897,965
8 transactions · 6 stateful · 2026-05-16 04:45:46 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,897,965 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd7ed05f0…6cbf
0x065c9d…c394
4 touches
1 conflict
0x26932889…8cfa
0x065c9d…c394
3 touches
1 conflict
0xc3209a93…8f8e
0x065c9d…c394
3 touches
1 conflict
0x24d5dbd4…3de6
0x065c9d…c394
2 touches
0 conflicts
0xb5a44030…5c28
0x065c9d…c394
2 touches
0 conflicts
0xcdd4bbf0…76e1
0x065c9d…c394
2 touches
0 conflicts
0xe566af4d…888d
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
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 0xd7ed05f006…8d6cbf
Audit this contract →
← previous block·next block →recent activity