Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: bdf67ff7fdb9661fa40cd652ec5be02a14f7aeb69398e59260f9e73ecf469fe2

Tx prefix hash: 4efffbe8cb929f357dccbd50802f0836fb982c1043a000de5bd1d9ac30ab9321
Tx public key: c075711ba0cc70f416a040ccaf7a7ade3f209e169395ae8d9e8ca448d9bb0408
Timestamp: 1747429168 Timestamp [UTC]: 2025-05-16 20:59:28 Age [y:d:h:m:s]: 01:012:00:10:49
Block: 1284420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 261195 RingCT/type: yes/0
Extra: 01c075711ba0cc70f416a040ccaf7a7ade3f209e169395ae8d9e8ca448d9bb04080211000000029f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ddd4fdfd41af027fe6409f1bf9ff45ffdd86f0cc83423494352724b963eb3ada 0.000600000000 1771875 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1284430, "vin": [ { "gen": { "height": 1284420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddd4fdfd41af027fe6409f1bf9ff45ffdd86f0cc83423494352724b963eb3ada" } } ], "extra": [ 1, 192, 117, 113, 27, 160, 204, 112, 244, 22, 160, 64, 204, 175, 122, 122, 222, 63, 32, 158, 22, 147, 149, 174, 141, 158, 140, 164, 72, 217, 187, 4, 8, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: