← previous blocknext block →recent activity
Analyzing
Block #74,606,072
28 transactions · 22 stateful · 2026-05-14 20:17:51 UTC
Parallelism
75/100
Blocked
59%
Avg conflicts / tx
1.21
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #74,606,072 · 28 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w411w012w113w214w321w522w523w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xbbee74c2…567a
0x065c9d…c394
10 touches
10 conflicts
0x30276c1c…47b4
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xab3526…fa38
8 touches
6 conflicts
0x24968e6d…0132
0x065c9d…c394
8 touches
6 conflicts
0x765c236f…ff45
0x2a68ba…90c5
6 touches
3 conflicts
0x816881fb…e436
0x34b655…2a6f
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 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