Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63751aeb7aacf29be74e7d987e0f8e51b2a404e8effe2bb061e2db17bce4d684

Tx prefix hash: 8d79b0b7779b245a32e7b8e9c24c446b24babc5b377d598365989a3fb1c3e723
Tx public key: 0aad3bcae9ec348275adcbe6296bdd919203cd04e8b118a0755f990d257feb4d
Timestamp: 1694461033 Timestamp [UCT]: 2023-09-11 19:37:13 Age [y:d:h:m:s]: 01:274:18:17:42
Block: 846006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457482 RingCT/type: yes/0
Extra: 010aad3bcae9ec348275adcbe6296bdd919203cd04e8b118a0755f990d257feb4d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.965675005000 dcy

stealth address amount amount idx
00: 8f118d2df76c0fb2e240e616a237c108ce0ae132ec0fce80bd0c7806d15c226b 0.965675005000 1299442 of 0

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": 846016, "vin": [ { "gen": { "height": 846006 } } ], "vout": [ { "amount": 965675005, "target": { "key": "8f118d2df76c0fb2e240e616a237c108ce0ae132ec0fce80bd0c7806d15c226b" } } ], "extra": [ 1, 10, 173, 59, 202, 233, 236, 52, 130, 117, 173, 203, 230, 41, 107, 221, 145, 146, 3, 205, 4, 232, 177, 24, 160, 117, 95, 153, 13, 37, 127, 235, 77, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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