← previous blocknext block →recent activity
Analyzing
Block #74,385,767
12 transactions · 10 stateful · 2026-05-13 19:43:53 UTC
Parallelism
83/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,385,767 · 12 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeabd3931…c39e
0x065c9d…c394
4 touches
1 conflict
0x94df22a4…f5d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x32f6e1cc…e271
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
2 touches
0 conflicts
0x0872abbe…9c39
0x2a68ba…90c5
2 touches
0 conflicts
0x76e559a4…77fb
0x2a68ba…90c5
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 0xeabd393141…18c39e
Audit this contract →
← previous block·next block →recent activity