Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fce8853f4d576770c89024b31251ddaffd90b185ea652c1378f44d20e2e57140

Tx prefix hash: 8aaf7a4ce8c66851935058791c526b9b18ee09be4fcfe146361c1613e1e8f7ee
Tx public key: 66d800fa94f3dabb38628e0c531799a618f3135caa30e06c996abb50dc3f1c7f
Timestamp: 1584522037 Timestamp [UCT]: 2020-03-18 09:00:37 Age [y:d:h:m:s]: 04:324:07:32:42
Block: 84818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1127226 RingCT/type: yes/0
Extra: 0166d800fa94f3dabb38628e0c531799a618f3135caa30e06c996abb50dc3f1c7f021100000005e5e30634000000000000000000

1 output(s) for total of 321.355205046000 dcy

stealth address amount amount idx
00: 59e4f68a56bd0be0ad822a14d5f53e72593ea0d845af103c9149bd08fb4b0419 321.355205046000 153550 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": 84828, "vin": [ { "gen": { "height": 84818 } } ], "vout": [ { "amount": 321355205046, "target": { "key": "59e4f68a56bd0be0ad822a14d5f53e72593ea0d845af103c9149bd08fb4b0419" } } ], "extra": [ 1, 102, 216, 0, 250, 148, 243, 218, 187, 56, 98, 142, 12, 83, 23, 153, 166, 24, 243, 19, 92, 170, 48, 224, 108, 153, 106, 187, 80, 220, 63, 28, 127, 2, 17, 0, 0, 0, 5, 229, 227, 6, 52, 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