Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7236dcd008122cb63fa01ad7c10c7e57e9c85f895a75627aaf6b20448094226

Tx prefix hash: 54926a0e70976ae382123c117b7950d82b2ab11a049b91bf78c9ad066ace8d72
Tx public key: 022b8a8ef335cc36ee11316197f3a4aa77bb2c36d007ab1557857b7bd572aae6
Timestamp: 1738282912 Timestamp [UCT]: 2025-01-31 00:21:52 Age [y:d:h:m:s]: 00:142:18:21:21
Block: 1208712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101901 RingCT/type: yes/0
Extra: 01022b8a8ef335cc36ee11316197f3a4aa77bb2c36d007ab1557857b7bd572aae60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2df787fc29bc8c1f9c2e959dd60e32b726b226c3d64e1d80c6b0f74880e41dd 0.600000000000 1695445 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": 1208722, "vin": [ { "gen": { "height": 1208712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2df787fc29bc8c1f9c2e959dd60e32b726b226c3d64e1d80c6b0f74880e41dd" } } ], "extra": [ 1, 2, 43, 138, 142, 243, 53, 204, 54, 238, 17, 49, 97, 151, 243, 164, 170, 119, 187, 44, 54, 208, 7, 171, 21, 87, 133, 123, 123, 213, 114, 170, 230, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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