Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e6fb4242e91f7e37cf99748439fee225d704c0f504fa0b67ee764109b7edb6

Tx prefix hash: 2f1d635fe5745b4668cdf273de65e2a9d259e1b8439cd2c98da50282ca6313f6
Tx public key: dd1ee53d3f40cf17bea8d2513901830181099cda521d6188a5b333eca1424a4e
Timestamp: 1738160054 Timestamp [UCT]: 2025-01-29 14:14:14 Age [y:d:h:m:s]: 00:143:21:07:59
Block: 1207690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102723 RingCT/type: yes/0
Extra: 01dd1ee53d3f40cf17bea8d2513901830181099cda521d6188a5b333eca1424a4e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 545a0fa50fff3fa7050c8e2b9b143857cb3af261ff463ae51c0d5cf3274d6e3b 0.600000000000 1694415 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": 1207700, "vin": [ { "gen": { "height": 1207690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "545a0fa50fff3fa7050c8e2b9b143857cb3af261ff463ae51c0d5cf3274d6e3b" } } ], "extra": [ 1, 221, 30, 229, 61, 63, 64, 207, 23, 190, 168, 210, 81, 57, 1, 131, 1, 129, 9, 156, 218, 82, 29, 97, 136, 165, 179, 51, 236, 161, 66, 74, 78, 2, 17, 0, 0, 0, 3, 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