← previous blocknext block →recent activity
Analyzing
Block #73,375,483
16 transactions · 13 stateful · 2026-05-09 03:22:44 UTC
Parallelism
81/100
Blocked
31%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,375,483 · 16 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
3w06w18w09w111w012w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x4e766fad…79a6
0xc8689a…ee79
4 touches
1 conflict
0xe94e77ab…f017
0x8e764f…e322
4 touches
1 conflict
0xf0f673fd…37a7
0x8e764f…e322
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x90a13a85…8c93
0x065c9d…c394
4 touches
1 conflict
0xa7fe0d97…ae1c
0x2a68ba…90c5
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity