Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5deff2b3969585233ad0b4039433c2b8e93291fdb304c52dfc94be07f07a7f20

Tx prefix hash: 8e2c48050cc50aadfecf2a98a25f76f9e6103cb04f295b1066f5e86cec3cbc5e
Tx public key: 6be899844e46e0b4de823f866449b2a6a97106107412f7f56866fb962e47bce0
Timestamp: 1735058580 Timestamp [UCT]: 2024-12-24 16:43:00 Age [y:d:h:m:s]: 00:106:00:29:40
Block: 1182289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75548 RingCT/type: yes/0
Extra: 016be899844e46e0b4de823f866449b2a6a97106107412f7f56866fb962e47bce00211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8854468ed09abeb7cb71f20d3a3477a395ce1fc667dea1099e5b6c5068a7e4b9 0.600000000000 1668722 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": 1182299, "vin": [ { "gen": { "height": 1182289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8854468ed09abeb7cb71f20d3a3477a395ce1fc667dea1099e5b6c5068a7e4b9" } } ], "extra": [ 1, 107, 232, 153, 132, 78, 70, 224, 180, 222, 130, 63, 134, 100, 73, 178, 166, 169, 113, 6, 16, 116, 18, 247, 245, 104, 102, 251, 150, 46, 71, 188, 224, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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