Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d80e52a70342c50fc57e89a9afe46cd120e1e67b8caffb87150a5cc2be09054

Tx prefix hash: cfddb74b7ed694916a921a84dc94cb369da6746301630af4ac85ad03cacd1013
Tx public key: 40b53f0846f77fc0a4b5cf070b6b0e1aca133f3b340fcf1d0200d3fb31b747dd
Timestamp: 1706129534 Timestamp [UCT]: 2024-01-24 20:52:14 Age [y:d:h:m:s]: 01:280:20:17:28
Block: 942535 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 459535 RingCT/type: yes/0
Extra: 0140b53f0846f77fc0a4b5cf070b6b0e1aca133f3b340fcf1d0200d3fb31b747dd0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 269b06c35f98de43bb29595d22768c7ba36d8a454234de53a9a05f54e5b4d823 0.600000000000 1400709 of 15

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": 942545, "vin": [ { "gen": { "height": 942535 } } ], "vout": [ { "amount": 600000000, "target": { "key": "269b06c35f98de43bb29595d22768c7ba36d8a454234de53a9a05f54e5b4d823" } } ], "extra": [ 1, 64, 181, 63, 8, 70, 247, 127, 192, 164, 181, 207, 7, 11, 107, 14, 26, 202, 19, 63, 59, 52, 15, 207, 29, 2, 0, 211, 251, 49, 183, 71, 221, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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