Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 135139689b726330df7c0a46edd45fafbfc8637edcf82f95dbdc5cb14a6957ec

Tx prefix hash: 20eaeb5e51a7a36c31f7dc3c886faba48aa77a9ecf2f489cb05900854f969b46
Tx public key: a660d5ad5a8b6d5b9067705019fe003116321e20545fcf2bfb8405a1c5f11f70
Timestamp: 1709332861 Timestamp [UCT]: 2024-03-01 22:41:01 Age [y:d:h:m:s]: 01:039:14:04:46
Block: 969128 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289294 RingCT/type: yes/0
Extra: 01a660d5ad5a8b6d5b9067705019fe003116321e20545fcf2bfb8405a1c5f11f700211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 072f4dca02b33cb6a748c0474909e044b24643826de6e82fe5b421fc0ffdc924 0.600000000000 1428955 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": 969138, "vin": [ { "gen": { "height": 969128 } } ], "vout": [ { "amount": 600000000, "target": { "key": "072f4dca02b33cb6a748c0474909e044b24643826de6e82fe5b421fc0ffdc924" } } ], "extra": [ 1, 166, 96, 213, 173, 90, 139, 109, 91, 144, 103, 112, 80, 25, 254, 0, 49, 22, 50, 30, 32, 84, 95, 207, 43, 251, 132, 5, 161, 197, 241, 31, 112, 2, 17, 0, 0, 0, 6, 122, 156, 244, 199, 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