Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0b2336b3da4def19fd35d44bf33bfbc47b4f9d17be2de77e47b3f0355b459ac

Tx prefix hash: f768cee2e1525973a14d78c8c178a66de685f9e8a16a7511842415c6c847849b
Tx public key: 0d692877be96f4763b8f481e8e330c35a48b5320c420b4ca356b963566cddd16
Timestamp: 1714233660 Timestamp [UCT]: 2024-04-27 16:01:00 Age [y:d:h:m:s]: 00:323:09:55:39
Block: 1009746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231199 RingCT/type: yes/0
Extra: 010d692877be96f4763b8f481e8e330c35a48b5320c420b4ca356b963566cddd160211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5b8b49f71d64a2596d253d19a821d7e8b516c04788020a8ec2f94e616d4cd66a 0.600000000000 1471506 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": 1009756, "vin": [ { "gen": { "height": 1009746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5b8b49f71d64a2596d253d19a821d7e8b516c04788020a8ec2f94e616d4cd66a" } } ], "extra": [ 1, 13, 105, 40, 119, 190, 150, 244, 118, 59, 143, 72, 30, 142, 51, 12, 53, 164, 139, 83, 32, 196, 32, 180, 202, 53, 107, 150, 53, 102, 205, 221, 22, 2, 17, 0, 0, 0, 6, 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