Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c924ff86f18483c17ebc8f075676dd4a5d412646c9fa1e5eac9f2ad70aa80823

Tx prefix hash: 770a7d5e1643383cbd8d8de9d416416417a70057fb8c687b3564809883b3a239
Tx public key: fc630356842c96cd42d307f4c80efa0259cd5a0a3f5058023a8104fc0fb30359
Timestamp: 1763466471 Timestamp [UCT]: 2025-11-18 11:47:51 Age [y:d:h:m:s]: 00:009:19:41:26
Block: 1414792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7023 RingCT/type: yes/0
Extra: 01fc630356842c96cd42d307f4c80efa0259cd5a0a3f5058023a8104fc0fb30359021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d648d1c3f41e34f06165267a4c43fd97c16ebb533a465ab99b9b63aa1fde9c 0.600000000000 1903285 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": 1414802, "vin": [ { "gen": { "height": 1414792 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d648d1c3f41e34f06165267a4c43fd97c16ebb533a465ab99b9b63aa1fde9c" } } ], "extra": [ 1, 252, 99, 3, 86, 132, 44, 150, 205, 66, 211, 7, 244, 200, 14, 250, 2, 89, 205, 90, 10, 63, 80, 88, 2, 58, 129, 4, 252, 15, 179, 3, 89, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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