← previous blocknext block →recent activity
Analyzing
Block #74,472,747
12 transactions · 11 stateful · 2026-05-14 05:22:50 UTC
Parallelism
75/100
Blocked
27%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,472,747 · 12 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
1w07w18w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53931041…7060
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xb0f7225a…d3d1
0x065c9d…c394
4 touches
1 conflict
0x1becc129…4390
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbcd06409…ee3b
0x065c9d…c394
3 touches
1 conflict
0x70dd2b2e…f410
0x065c9d…c394
2 touches
0 conflicts
0xf4fe7152…fd88
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 0x539310417b…7a7060
Audit this contract →
← previous block·next block →recent activity