Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9574294bedec4762be9c9302cd748889672f4d3a5ebadb076e59ea09de99cac

Tx prefix hash: fa9f138760a2bc8908e0aa1a1fc48550f81274c3a8339833bd30367e0114505c
Tx public key: 960dedf2ef54b6c8dafdd0911df02bde6b772270a2fd5f7e69a328e0f358320a
Timestamp: 1738545188 Timestamp [UCT]: 2025-02-03 01:13:08 Age [y:d:h:m:s]: 00:359:12:47:02
Block: 1210866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254646 RingCT/type: yes/0
Extra: 01960dedf2ef54b6c8dafdd0911df02bde6b772270a2fd5f7e69a328e0f358320a0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c20f06294578aacc46a36b98e30df9cb9c243a56946ac078ecf1db61215d49e 0.600000000000 1697621 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": 1210876, "vin": [ { "gen": { "height": 1210866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c20f06294578aacc46a36b98e30df9cb9c243a56946ac078ecf1db61215d49e" } } ], "extra": [ 1, 150, 13, 237, 242, 239, 84, 182, 200, 218, 253, 208, 145, 29, 240, 43, 222, 107, 119, 34, 112, 162, 253, 95, 126, 105, 163, 40, 224, 243, 88, 50, 10, 2, 17, 0, 0, 0, 3, 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