Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac54ab3fad6f2a1d5b1eef6fad9a8037712a6060e05bca44244aafce2285e39f

Tx prefix hash: bd64bd22d97aafc3e4ee07b4aa659e30c7b38dce66a3668c27546e431bce9e73
Tx public key: ea8579fa4d2aaf857e9fa645dd4d773df9e0e0d849e76008904b5b9b697426d3
Timestamp: 1582101454 Timestamp [UCT]: 2020-02-19 08:37:34 Age [y:d:h:m:s]: 04:331:23:04:52
Block: 68028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129709 RingCT/type: yes/0
Extra: 01ea8579fa4d2aaf857e9fa645dd4d773df9e0e0d849e76008904b5b9b697426d3021100000002724f989b000000000000000000

1 output(s) for total of 365.254691400000 dcy

stealth address amount amount idx
00: 0503972b4d5cea0a233804def2edc8474f7731e5f839a24945c931d107544e14 365.254691400000 125314 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": 68038, "vin": [ { "gen": { "height": 68028 } } ], "vout": [ { "amount": 365254691400, "target": { "key": "0503972b4d5cea0a233804def2edc8474f7731e5f839a24945c931d107544e14" } } ], "extra": [ 1, 234, 133, 121, 250, 77, 42, 175, 133, 126, 159, 166, 69, 221, 77, 119, 61, 249, 224, 224, 216, 73, 231, 96, 8, 144, 75, 91, 155, 105, 116, 38, 211, 2, 17, 0, 0, 0, 2, 114, 79, 152, 155, 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