← previous blocknext block →recent activity
Analyzing
Block #73,681,930
17 transactions · 15 stateful · 2026-05-10 13:26:41 UTC
Parallelism
59/100
Blocked
53%
Avg conflicts / tx
1.53
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,681,930 · 17 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
4w05w06w17w18w29w210w311w412w513w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
10 touches
10 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
10 touches
10 conflicts
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x00000000…0004
0x6e182e…04d8
2 touches
0 conflicts
0x455b104f…3960
0xea1b8e…c5ec
2 touches
0 conflicts
0x57c874be…de5b
0xea1b8e…c5ec
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity