Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 124a95f582f41db7dbfc31baee13f0edcc0109a4abf2edfa75179c4ffafea4c8

Tx prefix hash: 657e1e077af4d10f1704c31e318585fcedfa5a7859ff4ce39480884c026ab4d4
Tx public key: d782d11e12ef83bd5764e542a93619fb08cc5c113504d0ccd0acf8d497e3c4ce
Timestamp: 1729307041 Timestamp [UCT]: 2024-10-19 03:04:01 Age [y:d:h:m:s]: 00:165:02:52:26
Block: 1134709 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117779 RingCT/type: yes/0
Extra: 01d782d11e12ef83bd5764e542a93619fb08cc5c113504d0ccd0acf8d497e3c4ce0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0aca3c664f8a23a81238c7dad536415cfb8f13a7ab80d01967279220ad8b5d70 0.600000000000 1618034 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": 1134719, "vin": [ { "gen": { "height": 1134709 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0aca3c664f8a23a81238c7dad536415cfb8f13a7ab80d01967279220ad8b5d70" } } ], "extra": [ 1, 215, 130, 209, 30, 18, 239, 131, 189, 87, 100, 229, 66, 169, 54, 25, 251, 8, 204, 92, 17, 53, 4, 208, 204, 208, 172, 248, 212, 151, 227, 196, 206, 2, 17, 0, 0, 0, 4, 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