Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82751362290ec8bf787d923ddad7e5b5df325b37d211e324c3a9a2ea73206e8

Tx prefix hash: 56704606885954ac0af96403813c44faf67a5da40e3dc59f9d8df8d51c471dd7
Tx public key: 661d85ff047acec75f7beaed133ff8c13959d598e7537d79dfeb8eaff443bfdd
Timestamp: 1579048373 Timestamp [UCT]: 2020-01-15 00:32:53 Age [y:d:h:m:s]: 04:308:21:46:36
Block: 45687 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1110291 RingCT/type: yes/0
Extra: 01661d85ff047acec75f7beaed133ff8c13959d598e7537d79dfeb8eaff443bfdd0211000000d017786bcf000000000000000000

1 output(s) for total of 433.140040395000 dcy

stealth address amount amount idx
00: 4c113fdc56d27b2171e51ff2ae5bd6b6191f72ab89d563c050324d5554a94d19 433.140040395000 83613 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": 45697, "vin": [ { "gen": { "height": 45687 } } ], "vout": [ { "amount": 433140040395, "target": { "key": "4c113fdc56d27b2171e51ff2ae5bd6b6191f72ab89d563c050324d5554a94d19" } } ], "extra": [ 1, 102, 29, 133, 255, 4, 122, 206, 199, 95, 123, 234, 237, 19, 63, 248, 193, 57, 89, 213, 152, 231, 83, 125, 121, 223, 235, 142, 175, 244, 67, 191, 221, 2, 17, 0, 0, 0, 208, 23, 120, 107, 207, 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