← previous blocknext block →recent activity
Analyzing
Block #72,221,961
10 transactions · 9 stateful · 2026-05-03 19:16:50 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,221,961 · 10 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
2w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x03d3969c…7fb3
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x53f526a4…dfdf
0x065c9d…c394
3 touches
1 conflict
0x38c6a26e…11cf
0x065c9d…c394
2 touches
0 conflicts
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x512705a6…3930
0x065c9d…c394
2 touches
0 conflicts
0xbe094a7f…539c
0x065c9d…c394
2 touches
0 conflicts
0xcde8399c…d07a
0x065c9d…c394
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 0x03d3969c6e…0a7fb3
Audit this contract →
← previous block·next block →recent activity