Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b33c55382ae0e578358c55cb49c9d28f6f73bef587c50d8e11cc89d6075bdd61

Tx prefix hash: 32dbc7cb083cb9db1204f5a358358dc65b60144dd10ebdaa7b909a87d3b86adf
Tx public key: 469b863cb73a914d2139e2e3130c0fc4280c61c7e542ee58a8eef21461d7ba12
Timestamp: 1709555449 Timestamp [UCT]: 2024-03-04 12:30:49 Age [y:d:h:m:s]: 00:326:12:40:11
Block: 970968 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233699 RingCT/type: yes/0
Extra: 01469b863cb73a914d2139e2e3130c0fc4280c61c7e542ee58a8eef21461d7ba1202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ae409b58415c0161c0075b423ea61dd96ff9dda874bedb73be9949d37ffc6fb 0.600000000000 1430841 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": 970978, "vin": [ { "gen": { "height": 970968 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ae409b58415c0161c0075b423ea61dd96ff9dda874bedb73be9949d37ffc6fb" } } ], "extra": [ 1, 70, 155, 134, 60, 183, 58, 145, 77, 33, 57, 226, 227, 19, 12, 15, 196, 40, 12, 97, 199, 229, 66, 238, 88, 168, 238, 242, 20, 97, 215, 186, 18, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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