Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaacfd5c0f7b944a29901d5313dd33854b30581f91e89eb4a507ff2a8691025a

Tx prefix hash: dd86fc2da54df5afd1ce74375c77ec0fb23a885085f82fd04a9836ea7dd7e4e5
Tx public key: d618c7bfa199d97992384be1dda27d837b5cda3711b780ffdffd634f8dcae884
Timestamp: 1609893196 Timestamp [UCT]: 2021-01-06 00:33:16 Age [y:d:h:m:s]: 04:048:18:53:48
Block: 174960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1050024 RingCT/type: yes/0
Extra: 01d618c7bfa199d97992384be1dda27d837b5cda3711b780ffdffd634f8dcae88402110000002cdf1e48bb000000000000000000

1 output(s) for total of 161.542034864000 dcy

stealth address amount amount idx
00: a204f10df9a5a88cd7e366dffe3481cbbd75545f3bff5e80a9e5a4b337bf9c4a 161.542034864000 333642 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": 174970, "vin": [ { "gen": { "height": 174960 } } ], "vout": [ { "amount": 161542034864, "target": { "key": "a204f10df9a5a88cd7e366dffe3481cbbd75545f3bff5e80a9e5a4b337bf9c4a" } } ], "extra": [ 1, 214, 24, 199, 191, 161, 153, 217, 121, 146, 56, 75, 225, 221, 162, 125, 131, 123, 92, 218, 55, 17, 183, 128, 255, 223, 253, 99, 79, 141, 202, 232, 132, 2, 17, 0, 0, 0, 44, 223, 30, 72, 187, 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