← previous blocknext block →recent activity
Analyzing
Block #72,975,759
12 transactions · 9 stateful · 2026-05-07 07:03:10 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,975,759 · 12 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
4w06w110w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab760535…5df2
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0df972b1…7722
0x065c9d…c394
4 touches
1 conflict
0x069a3045…40cb
0x065c9d…c394
3 touches
1 conflict
0x4c1ba598…c776
0x065c9d…c394
3 touches
1 conflict
0xd7fc1d07…a279
0x065c9d…c394
2 touches
0 conflicts
0xe8772e48…e80c
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 0xab76053586…305df2
Audit this contract →
← previous block·next block →recent activity