← previous blocknext block →recent activity
Analyzing
Block #74,210,352
7 transactions · 6 stateful · 2026-05-13 00:17:09 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,210,352 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xbbee74c2…567a
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
2 touches
0 conflicts
0x406d501e…5a30
0x065c9d…c394
2 touches
0 conflicts
0x60d554d6…4d4c
0x065c9d…c394
2 touches
0 conflicts
0x7cb87cb1…c54a
0x065c9d…c394
2 touches
0 conflicts
0x8437e96b…fe65
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity