Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9db491f2f09f7f7d6d5ea5167759ceabdbdd7555d70aef0107e1199eb620df89

Tx prefix hash: 79830448b1bf905f06c62a378413c8a57463ab7702db6c906aeb5a2a37816243
Tx public key: cde37dc4250f4b83939a74c79014983c1fef30cb8c8190cf441f0db4f96a5f32
Timestamp: 1737789937 Timestamp [UCT]: 2025-01-25 07:25:37 Age [y:d:h:m:s]: 00:143:10:43:44
Block: 1204843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102268 RingCT/type: yes/0
Extra: 01cde37dc4250f4b83939a74c79014983c1fef30cb8c8190cf441f0db4f96a5f3202110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77968a5a86b729e6fea1b13a113f24b4316b2babbadc28591780afd4d2bbb750 0.600000000000 1691536 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": 1204853, "vin": [ { "gen": { "height": 1204843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77968a5a86b729e6fea1b13a113f24b4316b2babbadc28591780afd4d2bbb750" } } ], "extra": [ 1, 205, 227, 125, 196, 37, 15, 75, 131, 147, 154, 116, 199, 144, 20, 152, 60, 31, 239, 48, 203, 140, 129, 144, 207, 68, 31, 13, 180, 249, 106, 95, 50, 2, 17, 0, 0, 0, 11, 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