Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f80621dea0193874b2cda5ace8f34f1b61ee08e5f0dacf35bf21b2b0d7acad0

Tx prefix hash: e1669754e767d692a4dc0ea5bb3b2d86e7da9f57ea79beafb8683f98b94d5e2e
Tx public key: 84af6ab0b5bf78abc181f71008cee5cacac773f545a6842a685d8ddbc4f69a8b
Timestamp: 1725957397 Timestamp [UCT]: 2024-09-10 08:36:37 Age [y:d:h:m:s]: 00:220:14:57:39
Block: 1106948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157531 RingCT/type: yes/0
Extra: 0184af6ab0b5bf78abc181f71008cee5cacac773f545a6842a685d8ddbc4f69a8b02110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01c65ee2d95b3c5a4e4adeef3a9e8d45db0e8914b441f21b82ada922faa4b700 0.600000000000 1584553 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": 1106958, "vin": [ { "gen": { "height": 1106948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01c65ee2d95b3c5a4e4adeef3a9e8d45db0e8914b441f21b82ada922faa4b700" } } ], "extra": [ 1, 132, 175, 106, 176, 181, 191, 120, 171, 193, 129, 247, 16, 8, 206, 229, 202, 202, 199, 115, 245, 69, 166, 132, 42, 104, 93, 141, 219, 196, 246, 154, 139, 2, 17, 0, 0, 0, 11, 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