Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0a38bc766366b4a18931a4f1cc9fb9a30afefec764cd33ece7df828d5481c4

Tx prefix hash: af19e5fef238ad3dcbb01d878c513a52ce40d55e7ac1aa3b5f7ef2535874f019
Tx public key: fda806f24fe869d9a9c8d564d628b33dcc9f8a049dd3240ebbc8cb58e3c209ee
Timestamp: 1582797993 Timestamp [UCT]: 2020-02-27 10:06:33 Age [y:d:h:m:s]: 04:304:23:23:27
Block: 72525 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1111673 RingCT/type: yes/0
Extra: 01fda806f24fe869d9a9c8d564d628b33dcc9f8a049dd3240ebbc8cb58e3c209ee0211000000017adf42d3000000000000000000

1 output(s) for total of 352.935519808000 dcy

stealth address amount amount idx
00: 529fa6d57fb26434dd1f5bf8d91a31382caff6c2d3f12bd8fdb7d2b3c57412ec 352.935519808000 134038 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": 72535, "vin": [ { "gen": { "height": 72525 } } ], "vout": [ { "amount": 352935519808, "target": { "key": "529fa6d57fb26434dd1f5bf8d91a31382caff6c2d3f12bd8fdb7d2b3c57412ec" } } ], "extra": [ 1, 253, 168, 6, 242, 79, 232, 105, 217, 169, 200, 213, 100, 214, 40, 179, 61, 204, 159, 138, 4, 157, 211, 36, 14, 187, 200, 203, 88, 227, 194, 9, 238, 2, 17, 0, 0, 0, 1, 122, 223, 66, 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