Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6dab0bbec8c4492872269fd6822542f3200877423a1dc5fbe8fd734e51a03ca8

Tx prefix hash: 8e5ca0b4b9c81ce48319a0ce4dd51829404406a8fdfb5af38b155dd59deea64b
Tx public key: 7a52a63c918e1fd3c0697fb259ea7677de037a0ca0ea5c9adbdb54a03a0af799
Timestamp: 1733805434 Timestamp [UCT]: 2024-12-10 04:37:14 Age [y:d:h:m:s]: 00:140:03:38:39
Block: 1171915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99980 RingCT/type: yes/0
Extra: 017a52a63c918e1fd3c0697fb259ea7677de037a0ca0ea5c9adbdb54a03a0af7990211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf43e3c512f9af96c8dbc67bc503d0c7ccece53cebb5a0e90d10bbb51a48e08b 0.600000000000 1657738 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": 1171925, "vin": [ { "gen": { "height": 1171915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf43e3c512f9af96c8dbc67bc503d0c7ccece53cebb5a0e90d10bbb51a48e08b" } } ], "extra": [ 1, 122, 82, 166, 60, 145, 142, 31, 211, 192, 105, 127, 178, 89, 234, 118, 119, 222, 3, 122, 12, 160, 234, 92, 154, 219, 219, 84, 160, 58, 10, 247, 153, 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