Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49dafbccd5870fced501b01a1d5b35ed3fac040ced0b3fb8f4d99b5d15992ddd

Tx prefix hash: cb27623a4e6695246b3cf09ba381a9975615139c66fb225cb265b2eee7b38b1c
Tx public key: 392c8e5e9ded6cf83b8707803b8c868905538ce43e39247425178009a116d95d
Timestamp: 1578434672 Timestamp [UCT]: 2020-01-07 22:04:32 Age [y:d:h:m:s]: 04:324:09:24:54
Block: 40801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1121166 RingCT/type: yes/0
Extra: 01392c8e5e9ded6cf83b8707803b8c868905538ce43e39247425178009a116d95d021100000005391a8d0e000000000000000000

1 output(s) for total of 449.583326281000 dcy

stealth address amount amount idx
00: 7cc1593e6234031e5f1081b95b242e0e036da47bbb7e5791d6a5f9df53b87744 449.583326281000 72007 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": 40811, "vin": [ { "gen": { "height": 40801 } } ], "vout": [ { "amount": 449583326281, "target": { "key": "7cc1593e6234031e5f1081b95b242e0e036da47bbb7e5791d6a5f9df53b87744" } } ], "extra": [ 1, 57, 44, 142, 94, 157, 237, 108, 248, 59, 135, 7, 128, 59, 140, 134, 137, 5, 83, 140, 228, 62, 57, 36, 116, 37, 23, 128, 9, 161, 22, 217, 93, 2, 17, 0, 0, 0, 5, 57, 26, 141, 14, 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