Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b73d164c8098cd693546c75b6562ad61a4619db46727a71fb27b197d79ce2241

Tx prefix hash: 049230f0a59600e2ab0b79631d1e8405bd3408d5bdb261403f66d4ce9bc139a4
Tx public key: bf8e1be2e830454f1c32a2c7855507d5bb7a5060fdd87ae90d6ec03aad2ec285
Timestamp: 1594001717 Timestamp [UCT]: 2020-07-06 02:15:17 Age [y:d:h:m:s]: 04:218:08:12:44
Block: 114333 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1100399 RingCT/type: yes/0
Extra: 01bf8e1be2e830454f1c32a2c7855507d5bb7a5060fdd87ae90d6ec03aad2ec2850211000000068a2ee0d9000000000000000000

1 output(s) for total of 256.547655892000 dcy

stealth address amount amount idx
00: 71bcc0c3ba662d087a35b9621134a4c83f6cfeeb550e1c4e58864da88cb88270 256.547655892000 196385 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": 114343, "vin": [ { "gen": { "height": 114333 } } ], "vout": [ { "amount": 256547655892, "target": { "key": "71bcc0c3ba662d087a35b9621134a4c83f6cfeeb550e1c4e58864da88cb88270" } } ], "extra": [ 1, 191, 142, 27, 226, 232, 48, 69, 79, 28, 50, 162, 199, 133, 85, 7, 213, 187, 122, 80, 96, 253, 216, 122, 233, 13, 110, 192, 58, 173, 46, 194, 133, 2, 17, 0, 0, 0, 6, 138, 46, 224, 217, 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