Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caa4c84a20bb139c12f5057f9c3dd81f08eabc1f5593d3dd3f8a80ba56e3037e

Tx prefix hash: ccd9e878dea8e64c43e259e8570ae810db6913d458505b36ace29eab2d279339
Tx public key: b400d3c07cc9056794e0748e8bd63014d65fd8b719be7c0a875c8809e0510e61
Timestamp: 1725615465 Timestamp [UCT]: 2024-09-06 09:37:45 Age [y:d:h:m:s]: 00:203:09:15:19
Block: 1104116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145195 RingCT/type: yes/0
Extra: 01b400d3c07cc9056794e0748e8bd63014d65fd8b719be7c0a875c8809e0510e61021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6ccebb300024a3ac653a53d2f2b6a982bf227595c6ac974205a496696376fd1 0.600000000000 1581187 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": 1104126, "vin": [ { "gen": { "height": 1104116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6ccebb300024a3ac653a53d2f2b6a982bf227595c6ac974205a496696376fd1" } } ], "extra": [ 1, 180, 0, 211, 192, 124, 201, 5, 103, 148, 224, 116, 142, 139, 214, 48, 20, 214, 95, 216, 183, 25, 190, 124, 10, 135, 92, 136, 9, 224, 81, 14, 97, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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