Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cde4db7c32be688c7b4765f1020a9920f7932a612724897e7151fcec2edd1ce

Tx prefix hash: 3b184c058bf7014c6a61c4cc79c944f25767cd115d65aaf6bee5687ad5c3a4d7
Tx public key: c6c7abfd1d7efe8c8e46b8125604033c9b5162e8cc7c933f54aed22d5159e3ac
Timestamp: 1638273423 Timestamp [UCT]: 2021-11-30 11:57:03 Age [y:d:h:m:s]: 03:069:23:44:21
Block: 385356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 828696 RingCT/type: yes/0
Extra: 01c6c7abfd1d7efe8c8e46b8125604033c9b5162e8cc7c933f54aed22d5159e3ac021100000001536c63bb000000000000000000

1 output(s) for total of 32.445612419000 dcy

stealth address amount amount idx
00: a2c0bb30e6d3faba2ac4a45ce254a5051922d9376cd61a4a703c036d0fa41f87 32.445612419000 777663 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": 385366, "vin": [ { "gen": { "height": 385356 } } ], "vout": [ { "amount": 32445612419, "target": { "key": "a2c0bb30e6d3faba2ac4a45ce254a5051922d9376cd61a4a703c036d0fa41f87" } } ], "extra": [ 1, 198, 199, 171, 253, 29, 126, 254, 140, 142, 70, 184, 18, 86, 4, 3, 60, 155, 81, 98, 232, 204, 124, 147, 63, 84, 174, 210, 45, 81, 89, 227, 172, 2, 17, 0, 0, 0, 1, 83, 108, 99, 187, 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