Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e46d9dfc22fbb77dceae42d8254776d4dbffcb1f6792e9996abd1e13cb7d7fe

Tx prefix hash: ec46b67df11e751f403c47ba6a6944263e1da1fbc0cc24e517d05a90571ccba1
Tx public key: dd35a472a1846830908fd653049cca0bdcd7d8999ee714c337c0f48ea3926e93
Timestamp: 1733627069 Timestamp [UCT]: 2024-12-08 03:04:29 Age [y:d:h:m:s]: 00:105:02:24:51
Block: 1170431 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74907 RingCT/type: yes/0
Extra: 01dd35a472a1846830908fd653049cca0bdcd7d8999ee714c337c0f48ea3926e93021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 530cd13c0f1dd92b4aca470ae2bb7163a2869b51a7dad47d2f8e1bdc7b074e37 0.600000000000 1656162 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": 1170441, "vin": [ { "gen": { "height": 1170431 } } ], "vout": [ { "amount": 600000000, "target": { "key": "530cd13c0f1dd92b4aca470ae2bb7163a2869b51a7dad47d2f8e1bdc7b074e37" } } ], "extra": [ 1, 221, 53, 164, 114, 161, 132, 104, 48, 144, 143, 214, 83, 4, 156, 202, 11, 220, 215, 216, 153, 158, 231, 20, 195, 55, 192, 244, 142, 163, 146, 110, 147, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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