← previous blocknext block →recent activity
Analyzing
Block #72,975,655
8 transactions · 6 stateful · 2026-05-07 07:02:28 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,975,655 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc14fa872…b23e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc1c72683…1b7b
0x065c9d…c394
3 touches
1 conflict
0x02c13b2d…64e5
0x065c9d…c394
2 touches
0 conflicts
0x0b390c61…dc07
0x065c9d…c394
2 touches
0 conflicts
0x37ef5178…fec7
0x065c9d…c394
2 touches
0 conflicts
0x66b87e26…793d
0x065c9d…c394
2 touches
0 conflicts
0x9c762a38…1af7
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 0xc14fa8724a…2fb23e
Audit this contract →
← previous block·next block →recent activity