Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3527105eaebf4eb3313812075387982d5629c75464d371fcc9c8b1db2c4df88

Tx prefix hash: f042726712cce4c39194c17bcf0af881489a28b80fe92329882803f3ca969f06
Tx public key: ec3f2a4cb3c8a66d87206c43d2abd7cca7b8deb98f30e341a1cb434bbb6f8bcc
Timestamp: 1715362252 Timestamp [UCT]: 2024-05-10 17:30:52 Age [y:d:h:m:s]: 00:342:16:40:20
Block: 1019104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244969 RingCT/type: yes/0
Extra: 01ec3f2a4cb3c8a66d87206c43d2abd7cca7b8deb98f30e341a1cb434bbb6f8bcc02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 145e65c28b77497c1b700d470e049d9cb89558236e6a14b5757ef849fe923640 0.600000000000 1482987 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": 1019114, "vin": [ { "gen": { "height": 1019104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "145e65c28b77497c1b700d470e049d9cb89558236e6a14b5757ef849fe923640" } } ], "extra": [ 1, 236, 63, 42, 76, 179, 200, 166, 109, 135, 32, 108, 67, 210, 171, 215, 204, 167, 184, 222, 185, 143, 48, 227, 65, 161, 203, 67, 75, 187, 111, 139, 204, 2, 17, 0, 0, 0, 6, 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