Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66f44578d0c1a08bcd8092dd1fbc73a4e9d8287f178197e25be4b62b65339b05

Tx prefix hash: e5bf53402a7a921d4bf686bf61a9dd1ccf1f03780e65cc91939ba1d9914943d1
Tx public key: 0a9f0e10172876800afb9eb8e7786acbf082ac18a6909f22df08b8e0bce945b2
Timestamp: 1582974009 Timestamp [UCT]: 2020-02-29 11:00:09 Age [y:d:h:m:s]: 05:072:02:36:54
Block: 73963 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1205941 RingCT/type: yes/0
Extra: 010a9f0e10172876800afb9eb8e7786acbf082ac18a6909f22df08b8e0bce945b202110000010f56c366d3000000000000000000

1 output(s) for total of 349.084588843000 dcy

stealth address amount amount idx
00: 0e11fb974e1efbb4a6504e1da81dc6022c0a66a3a08e1ece1cecc21adf374ce5 349.084588843000 136696 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": 73973, "vin": [ { "gen": { "height": 73963 } } ], "vout": [ { "amount": 349084588843, "target": { "key": "0e11fb974e1efbb4a6504e1da81dc6022c0a66a3a08e1ece1cecc21adf374ce5" } } ], "extra": [ 1, 10, 159, 14, 16, 23, 40, 118, 128, 10, 251, 158, 184, 231, 120, 106, 203, 240, 130, 172, 24, 166, 144, 159, 34, 223, 8, 184, 224, 188, 233, 69, 178, 2, 17, 0, 0, 1, 15, 86, 195, 102, 211, 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