← previous blocknext block →recent activity
Analyzing
Block #72,458,584
12 transactions · 12 stateful · 2026-05-04 21:37:36 UTC
Parallelism
50/100
Blocked
50%
Avg conflicts / tx
1.42
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #72,458,584 · 12 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
1w02w13w25w26w37w49w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd6d760a0…0c1b
0x065c9d…c394
9 touches
10 conflicts
0x5510492e…90f7
0xd32edf…ff58
9 touches
10 conflicts
0xc3c8642a…7da5
0x2a68ba…90c5
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c3
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
4 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
10 conflicts on slot 0xd6d760a0ae…c30c1b
Audit this contract →
← previous block·next block →recent activity