Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35533f95461dbc26bd1170bd3345fa22c52eaf1041b5b8929dce70ce97f2c59a

Tx prefix hash: 5b04477564da0b08bc9f02625d6f84eb7b0cc95543f51bdedb38a3191a4771a8
Tx public key: cf2602f35b058dbf2ded0eaeaa1c2c7da2827412ebebba40d4b1fefa30259f82
Timestamp: 1764651546 Timestamp [UCT]: 2025-12-02 04:59:06 Age [y:d:h:m:s]: 00:058:01:41:08
Block: 1424604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41400 RingCT/type: yes/0
Extra: 01cf2602f35b058dbf2ded0eaeaa1c2c7da2827412ebebba40d4b1fefa30259f820211000000074e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaae729365a556d51403fa33075a19fd4eb0bbb1bbaa95b26f21c2a43b17ba79 0.600000000000 1913235 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": 1424614, "vin": [ { "gen": { "height": 1424604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaae729365a556d51403fa33075a19fd4eb0bbb1bbaa95b26f21c2a43b17ba79" } } ], "extra": [ 1, 207, 38, 2, 243, 91, 5, 141, 191, 45, 237, 14, 174, 170, 28, 44, 125, 162, 130, 116, 18, 235, 235, 186, 64, 212, 177, 254, 250, 48, 37, 159, 130, 2, 17, 0, 0, 0, 7, 78, 123, 252, 9, 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