← previous blocknext block →recent activity
Analyzing
Block #73,743,769
16 transactions · 15 stateful · 2026-05-10 20:23:51 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
1.69
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,743,769 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w010w111w212w313w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0xf1213d61…614e
0x065c9d…c394
2 touches
0 conflicts
0x82992591…9ff0
0x371c7e…2f07
2 touches
0 conflicts
0x00000000…0066
0x98a5d8…a3c2
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity