← previous blocknext block →recent activity
Analyzing
Block #72,971,796
17 transactions · 13 stateful · 2026-05-07 06:36:47 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,971,796 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w07w18w19w210w313w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xce7bfe5e…5e58
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xb12f045f…5f77
0xd32edf…ff58
3 touches
1 conflict
0x6be305d2…e544
0x065c9d…c394
2 touches
0 conflicts
0xc35101fd…3f48
0x065c9d…c394
2 touches
0 conflicts
0xe3435e13…f21a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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
6 conflicts on slot 0xce7bfe5ef1…205e58
Audit this contract →
← previous block·next block →recent activity