Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a38ff6b27a1ce3b9782dcd12dbceda84bafb88edcc5756a67388fea3c0cdd924

Tx prefix hash: a56809cc39f34117e418769eec7a36a64a5cdd761789f2590636092cc898e698
Tx public key: d2e4b0a3684dba72634aa4e25966c3116ad386897bbb2b96d3186d5f8355ce76
Timestamp: 1723859010 Timestamp [UCT]: 2024-08-17 01:43:30 Age [y:d:h:m:s]: 00:276:02:38:08
Block: 1089549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197241 RingCT/type: yes/0
Extra: 01d2e4b0a3684dba72634aa4e25966c3116ad386897bbb2b96d3186d5f8355ce76021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02a9a16462c3d3b7e14d4882e3ee8c57ef5dbfb405f7b6df4864b532f9576d91 0.600000000000 1564172 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": 1089559, "vin": [ { "gen": { "height": 1089549 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02a9a16462c3d3b7e14d4882e3ee8c57ef5dbfb405f7b6df4864b532f9576d91" } } ], "extra": [ 1, 210, 228, 176, 163, 104, 77, 186, 114, 99, 74, 164, 226, 89, 102, 195, 17, 106, 211, 134, 137, 123, 187, 43, 150, 211, 24, 109, 95, 131, 85, 206, 118, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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