Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dfbd8e15a51ce3f1cf93fc4e8db8b993ae1a5f31f5dfa741d5af0e64250fc395

Tx prefix hash: 497c00352fde96a91a89a95f2edc668ab2e3c3423568dc302af0749a4bf0d8b7
Tx public key: 415d1448233810e3dc583411b33c8cda19a49539cb6392eb0700cf69b7139316
Timestamp: 1736658248 Timestamp [UCT]: 2025-01-12 05:04:08 Age [y:d:h:m:s]: 00:157:08:53:08
Block: 1195514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112181 RingCT/type: yes/0
Extra: 01415d1448233810e3dc583411b33c8cda19a49539cb6392eb0700cf69b71393160211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 410d47ab4f5acd0fae3daaff3add5a4095773a055af64eea64f46d1fe7b6df73 0.600000000000 1682105 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": 1195524, "vin": [ { "gen": { "height": 1195514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "410d47ab4f5acd0fae3daaff3add5a4095773a055af64eea64f46d1fe7b6df73" } } ], "extra": [ 1, 65, 93, 20, 72, 35, 56, 16, 227, 220, 88, 52, 17, 179, 60, 140, 218, 25, 164, 149, 57, 203, 99, 146, 235, 7, 0, 207, 105, 183, 19, 147, 22, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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