← previous blocknext block →recent activity
Analyzing
Block #72,500,568
10 transactions · 9 stateful · 2026-05-05 02:17:02 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,500,568 · 10 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
1w03w16w07w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x113b3a26…4a92
0x065c9d…c394
2 touches
0 conflicts
0x121c0ed5…50e8
0x065c9d…c394
2 touches
0 conflicts
0x1b909973…4a05
0x065c9d…c394
2 touches
0 conflicts
0x24e855ea…04bb
0x065c9d…c394
2 touches
0 conflicts
0x72e9a6f4…75f3
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