← previous blocknext block →recent activity
Analyzing
Block #72,295,936
8 transactions · 8 stateful · 2026-05-04 03:33:53 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,295,936 · 8 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfc7ae09c…2d21
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x11b9474e…f282
0x065c9d…c394
4 touches
1 conflict
0x13867ad2…5a99
0x065c9d…c394
3 touches
1 conflict
0x65ab6422…a3be
0x065c9d…c394
3 touches
1 conflict
0x88b28eda…4c7b
0x065c9d…c394
3 touches
1 conflict
0x00000000…0018
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0028
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
1 conflict on slot 0xfc7ae09c5b…7d2d21
Audit this contract →
← previous block·next block →recent activity