Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc43a55152f6ee8535c9354c32b2bc9620639776b00d3502285d3bcd46a23f3b

Tx prefix hash: bb4850555d3a35df32a7d91eab08050dfdd9f73acab7cc8d6b186d4d5ae96e48
Tx public key: 4fec9d33dd6a9e49c918b572aa903be66446d838d158f23145e1a5d67e8dff8b
Timestamp: 1763460088 Timestamp [UCT]: 2025-11-18 10:01:28 Age [y:d:h:m:s]: 00:009:20:10:42
Block: 1414736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7046 RingCT/type: yes/0
Extra: 014fec9d33dd6a9e49c918b572aa903be66446d838d158f23145e1a5d67e8dff8b021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f98d9bf63430c7023656335717883876775f09ec3b001b153ed1bd4e44c3df39 0.600000000000 1903227 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": 1414746, "vin": [ { "gen": { "height": 1414736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98d9bf63430c7023656335717883876775f09ec3b001b153ed1bd4e44c3df39" } } ], "extra": [ 1, 79, 236, 157, 51, 221, 106, 158, 73, 201, 24, 181, 114, 170, 144, 59, 230, 100, 70, 216, 56, 209, 88, 242, 49, 69, 225, 165, 214, 126, 141, 255, 139, 2, 17, 0, 0, 0, 2, 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