Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985fa47c8371ffbe34d4be40a3db41ec878d67e1bef978b5c6532f6fe4a00870

Tx prefix hash: 8269e405a703ee2a2d65e3f52d96d9533d9356bb62bc02bcb52bd6781c7c0feb
Tx public key: e5638c532485849061d3cba458454c219d8d6896274a8799d0a47a90ce6da6cf
Timestamp: 1691525841 Timestamp [UCT]: 2023-08-08 20:17:21 Age [y:d:h:m:s]: 02:084:12:35:15
Block: 821747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 580076 RingCT/type: yes/0
Extra: 01e5638c532485849061d3cba458454c219d8d6896274a8799d0a47a90ce6da6cf02110000000375e3f0e9000000000000000000

1 output(s) for total of 1.162013473000 dcy

stealth address amount amount idx
00: 8455eccb24b28d89a580cd4cbc3ff74981e5e2033bfffb618e49c45dbbc36c5e 1.162013473000 1273873 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": 821757, "vin": [ { "gen": { "height": 821747 } } ], "vout": [ { "amount": 1162013473, "target": { "key": "8455eccb24b28d89a580cd4cbc3ff74981e5e2033bfffb618e49c45dbbc36c5e" } } ], "extra": [ 1, 229, 99, 140, 83, 36, 133, 132, 144, 97, 211, 203, 164, 88, 69, 76, 33, 157, 141, 104, 150, 39, 74, 135, 153, 208, 164, 122, 144, 206, 109, 166, 207, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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