Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc3b18d9dae48e48c4e6742292ff064c22139f7f8a5c9eb7f872f002df92180d

Tx prefix hash: 3803260b9d1a2d9ce4a1b9c60c6c18707e9a024248e56146f0184121e21c2a11
Tx public key: 1f3754275473bfc3299cd210c6121e9c1f786c196e58f7552e47d577f2b9131b
Timestamp: 1577083444 Timestamp [UCT]: 2019-12-23 06:44:04 Age [y:d:h:m:s]: 04:343:05:02:13
Block: 29879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1134366 RingCT/type: yes/0
Extra: 011f3754275473bfc3299cd210c6121e9c1f786c196e58f7552e47d577f2b9131b02110000000d8a2ee0d9000000000000000000

1 output(s) for total of 488.651607846000 dcy

stealth address amount amount idx
00: 28bfb20f1fb45aa37801749f70a3ec4c4f701f8d152f03e9b930f55ca7f92e34 488.651607846000 49281 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": 29889, "vin": [ { "gen": { "height": 29879 } } ], "vout": [ { "amount": 488651607846, "target": { "key": "28bfb20f1fb45aa37801749f70a3ec4c4f701f8d152f03e9b930f55ca7f92e34" } } ], "extra": [ 1, 31, 55, 84, 39, 84, 115, 191, 195, 41, 156, 210, 16, 198, 18, 30, 156, 31, 120, 108, 25, 110, 88, 247, 85, 46, 71, 213, 119, 242, 185, 19, 27, 2, 17, 0, 0, 0, 13, 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