← previous blocknext block →recent activity
Analyzing
Block #73,808,834
12 transactions · 10 stateful · 2026-05-11 03:42:26 UTC
Parallelism
67/100
Blocked
30%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,808,834 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xedf04da2…3941
0xd32edf…ff58
3 touches
1 conflict
0x01724889…ca5b
0x065c9d…c394
2 touches
0 conflicts
0x26ed3870…ba62
0x065c9d…c394
2 touches
0 conflicts
0x671a84ea…0f09
0x065c9d…c394
2 touches
0 conflicts
0x67b05f27…1382
0x065c9d…c394
2 touches
0 conflicts
0x80e262d4…3193
0x065c9d…c394
2 touches
0 conflicts
0xb05acf48…a579
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity