Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da1f5cb4953bef0780f9a13c9e3700e8447962df30510a662036680189883cff

Tx prefix hash: 8edc31b314debf2ae6a7673f397d87bcd794ed660b99d7194387485cb22db5f0
Tx public key: 234cc040f71da0768e33ef6fc2ca1fa9cf51894a7e72f149a54f65a359b75762
Timestamp: 1581946902 Timestamp [UCT]: 2020-02-17 13:41:42 Age [y:d:h:m:s]: 04:275:13:07:23
Block: 66701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1089400 RingCT/type: yes/0
Extra: 01234cc040f71da0768e33ef6fc2ca1fa9cf51894a7e72f149a54f65a359b7576202110000000256c366d3000000000000000000

1 output(s) for total of 368.971402142000 dcy

stealth address amount amount idx
00: ffed459d9372d1c926b31a61fd8eb4b5a601c5f1f1641ed3adb53f1d5d34e953 368.971402142000 122866 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": 66711, "vin": [ { "gen": { "height": 66701 } } ], "vout": [ { "amount": 368971402142, "target": { "key": "ffed459d9372d1c926b31a61fd8eb4b5a601c5f1f1641ed3adb53f1d5d34e953" } } ], "extra": [ 1, 35, 76, 192, 64, 247, 29, 160, 118, 142, 51, 239, 111, 194, 202, 31, 169, 207, 81, 137, 74, 126, 114, 241, 73, 165, 79, 101, 163, 89, 183, 87, 98, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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