Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a0b4125534de997f9b89fdac10177b72f3159d9d5449d3ddecaefe281c18842

Tx prefix hash: 16334be1f105a49e47f95e6a169477da20570b8a0e1b3abd96e82de2bc1ebaa6
Tx public key: 70aa960505c2c45905483a040f02d9e1cd4ad529c3bb9f1989fc429e6d78069e
Timestamp: 1726471869 Timestamp [UCT]: 2024-09-16 07:31:09 Age [y:d:h:m:s]: 00:116:04:38:53
Block: 1111204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83094 RingCT/type: yes/0
Extra: 0170aa960505c2c45905483a040f02d9e1cd4ad529c3bb9f1989fc429e6d78069e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9bed561cd1d78f8d3038c3a9d6fdd9c67f7755cd65b3858a7b9b3e283872eb77 0.600000000000 1590083 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": 1111214, "vin": [ { "gen": { "height": 1111204 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9bed561cd1d78f8d3038c3a9d6fdd9c67f7755cd65b3858a7b9b3e283872eb77" } } ], "extra": [ 1, 112, 170, 150, 5, 5, 194, 196, 89, 5, 72, 58, 4, 15, 2, 217, 225, 205, 74, 213, 41, 195, 187, 159, 25, 137, 252, 66, 158, 109, 120, 6, 158, 2, 17, 0, 0, 0, 9, 233, 20, 221, 21, 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