Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01d65f0d1bccf67c7feb35c2b285ed06ddc549521ed8bc96d322824a8dc35aed

Tx prefix hash: 9ad411dc4c61c27c53a851a296e52fa94583d8ed17e84600859c34cda6fc246f
Tx public key: 2c2c7aca1101bd5fd6ba8f939033515b3783c7b9eb2c45339fe91313ea403b7b
Timestamp: 1672851834 Timestamp [UCT]: 2023-01-04 17:03:54 Age [y:d:h:m:s]: 02:111:19:17:08
Block: 667548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601600 RingCT/type: yes/0
Extra: 012c2c7aca1101bd5fd6ba8f939033515b3783c7b9eb2c45339fe91313ea403b7b021100000002e6d27f9c000000000000000000

1 output(s) for total of 3.768220644000 dcy

stealth address amount amount idx
00: ed87165c3e2713b3c75715e307bdcf4bd1bfc4ffd5a5d3eb3a833555901f0e88 3.768220644000 1108761 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": 667558, "vin": [ { "gen": { "height": 667548 } } ], "vout": [ { "amount": 3768220644, "target": { "key": "ed87165c3e2713b3c75715e307bdcf4bd1bfc4ffd5a5d3eb3a833555901f0e88" } } ], "extra": [ 1, 44, 44, 122, 202, 17, 1, 189, 95, 214, 186, 143, 147, 144, 51, 81, 91, 55, 131, 199, 185, 235, 44, 69, 51, 159, 233, 19, 19, 234, 64, 59, 123, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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