← previous blocknext block →recent activity
Analyzing
Block #73,039,108
16 transactions · 12 stateful · 2026-05-07 14:04:49 UTC
Parallelism
69/100
Blocked
42%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,039,108 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w17w210w311w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xd574ca…7ab1
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
4 touches
1 conflict
0x70b2f813…783c
0x2a68ba…90c5
4 touches
1 conflict
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x4e5ebbf7…ae70
0xc8689a…ee79
4 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity