← previous blocknext block →recent activity
Analyzing
Block #73,358,549
11 transactions · 8 stateful · 2026-05-09 01:30:03 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,358,549 · 11 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
0x244ee2e5…400c
0x065c9d…c394
4 touches
1 conflict
0x58e1a3f3…ffca
0x065c9d…c394
3 touches
1 conflict
0xf1a7f46a…a51d
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x0c4de2e1…a293
0x065c9d…c394
2 touches
0 conflicts
0x426d806f…bcf6
0x065c9d…c394
2 touches
0 conflicts
0x87614c8e…bbd9
0x065c9d…c394
2 touches
0 conflicts
0x8fcbbd35…bf07
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 0x244ee2e592…f8400c
Audit this contract →
← previous block·next block →recent activity