Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c595e0e3a42882127a5a911b37ac8d57ca08e34fca85cadf371dac1b15027cec

Tx prefix hash: 73c92f8a2395497eafea5af30572e98b3e324618da981fd989b085fec3da688e
Tx public key: 119acfe753bb308a91fbddd72ed45d6bc56d9d65082df2a6229407d2f63e45f3
Timestamp: 1720258481 Timestamp [UCT]: 2024-07-06 09:34:41 Age [y:d:h:m:s]: 01:126:10:06:12
Block: 1059694 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348889 RingCT/type: yes/0
Extra: 01119acfe753bb308a91fbddd72ed45d6bc56d9d65082df2a6229407d2f63e45f302110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f2a34ab712f2d498d523efa065e5d5c1cdad343866b1090789d9c770f4c2d4d3 0.600000000000 1530165 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": 1059704, "vin": [ { "gen": { "height": 1059694 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f2a34ab712f2d498d523efa065e5d5c1cdad343866b1090789d9c770f4c2d4d3" } } ], "extra": [ 1, 17, 154, 207, 231, 83, 187, 48, 138, 145, 251, 221, 215, 46, 212, 93, 107, 197, 109, 157, 101, 8, 45, 242, 166, 34, 148, 7, 210, 246, 62, 69, 243, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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