Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf50162f197683c307d82ac8e09d4238ffb3070f0f3d7bc48c44fab8c8d332f

Tx prefix hash: e363b7fe2fd8534ee2173bf185bd389058f9f16883f7d45966d114fbbd14a6a6
Tx public key: 532b7a624189e73d55fdbf36b6a13beac2e3ba7d01f298f3501b19e372171a46
Timestamp: 1737379425 Timestamp [UCT]: 2025-01-20 13:23:45 Age [y:d:h:m:s]: 00:303:18:37:44
Block: 1201441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214666 RingCT/type: yes/0
Extra: 01532b7a624189e73d55fdbf36b6a13beac2e3ba7d01f298f3501b19e372171a46021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 988d8a7f644532a5d46207ce4c2a10cbf697e170186337d427bd80294c95c04f 0.600000000000 1688094 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 dinasty-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": 1201451, "vin": [ { "gen": { "height": 1201441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "988d8a7f644532a5d46207ce4c2a10cbf697e170186337d427bd80294c95c04f" } } ], "extra": [ 1, 83, 43, 122, 98, 65, 137, 231, 61, 85, 253, 191, 54, 182, 161, 59, 234, 194, 227, 186, 125, 1, 242, 152, 243, 80, 27, 25, 227, 114, 23, 26, 70, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8