← previous blocknext block →recent activity
Analyzing
Block #74,314,271
7 transactions · 7 stateful · 2026-05-13 11:48:19 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,314,271 · 7 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
2w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x542294a5…1fb1
0x065c9d…c394
2 touches
0 conflicts
0x5b8f493e…4d13
0x065c9d…c394
2 touches
0 conflicts
0x8a2a7a38…01bf
0x065c9d…c394
2 touches
0 conflicts
0x907861a3…bb60
0x065c9d…c394
2 touches
0 conflicts
0x97454acd…7653
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 0x24968e6db4…f00132
Audit this contract →
← previous block·next block →recent activity