Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 417a83314d0640a1d4dce61c756ecafcba0bbf809521c2200d18425f57c7445e

Tx prefix hash: c32992eff61cb496c68dd89d0ebe36e1872fe511dffce0c9598aade80ff10b46
Tx public key: e22215b41ab6d931531c6e99267a790f1f0d56b652f0cac0652d711aec6fb550
Timestamp: 1686080231 Timestamp [UCT]: 2023-06-06 19:37:11 Age [y:d:h:m:s]: 01:308:02:51:01
Block: 776587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 481403 RingCT/type: yes/0
Extra: 01e22215b41ab6d931531c6e99267a790f1f0d56b652f0cac0652d711aec6fb55002110000000175e3f0e9000000000000000000

1 output(s) for total of 1.640004564000 dcy

stealth address amount amount idx
00: b2f422605bbb9d5c2972a09d9b3bab18d19077c641c3ee3aac115d96413881b9 1.640004564000 1226144 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": 776597, "vin": [ { "gen": { "height": 776587 } } ], "vout": [ { "amount": 1640004564, "target": { "key": "b2f422605bbb9d5c2972a09d9b3bab18d19077c641c3ee3aac115d96413881b9" } } ], "extra": [ 1, 226, 34, 21, 180, 26, 182, 217, 49, 83, 28, 110, 153, 38, 122, 121, 15, 31, 13, 86, 182, 82, 240, 202, 192, 101, 45, 113, 26, 236, 111, 181, 80, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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