← previous blocknext block →recent activity
Analyzing
Block #73,434,495
7 transactions · 7 stateful · 2026-05-09 09:55:26 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,434,495 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x107c9d8c…097f
0x065c9d…c394
4 touches
1 conflict
0x0175b7a6…1dbc
0x6c4bfa…a540
4 touches
1 conflict
0x0175b7a6…1dbd
0x6c4bfa…a540
4 touches
1 conflict
0xed57bddf…1abf
0xc8689a…ee79
4 touches
1 conflict
0x0c89ea7e…13eb
0x6c4bfa…a540
3 touches
1 conflict
0x1a4b4152…0a08
0x6c4bfa…a540
3 touches
1 conflict
0x1f9b4577…35c8
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity