← previous blocknext block →recent activity
Analyzing
Block #74,460,545
14 transactions · 11 stateful · 2026-05-14 04:01:43 UTC
Parallelism
79/100
Blocked
27%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #74,460,545 · 14 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
1w02w13w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x37cc741d…7ed3
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xffe431af…8faa
0x065c9d…c394
4 touches
1 conflict
0xa59fb579…2edf
0x065c9d…c394
3 touches
1 conflict
0xaddbd143…332f
0x065c9d…c394
3 touches
1 conflict
0xf35ac73f…41e1
0xd32edf…ff58
3 touches
1 conflict
0xc830c641…e229
0x065c9d…c394
3 touches
1 conflict
0x7f75f56e…51c0
0x065c9d…c394
3 touches
1 conflict
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 0x37cc741d41…df7ed3
Audit this contract →
← previous block·next block →recent activity