Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a744b479614fc76ae25cc17b9f152392b50f33a328aab59bcb7d6805b2d431a

Tx prefix hash: 74219ad66e6d7bfd7c5d6abcb1825d1418a567d92e94c53a8b454d2a0a7681b1
Tx public key: 9b4ef1a64b81775d8f814a2f424668eb7deeae881e87fdb17c139b997b38701d
Timestamp: 1749321393 Timestamp [UCT]: 2025-06-07 18:36:33 Age [y:d:h:m:s]: 00:164:10:43:27
Block: 1300096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115213 RingCT/type: yes/0
Extra: 019b4ef1a64b81775d8f814a2f424668eb7deeae881e87fdb17c139b997b38701d02110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe55ca77b68f4a5f2025f746bc6060513f73adac0046838164cce5474e8b55f5 0.600000000000 1787643 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": 1300106, "vin": [ { "gen": { "height": 1300096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe55ca77b68f4a5f2025f746bc6060513f73adac0046838164cce5474e8b55f5" } } ], "extra": [ 1, 155, 78, 241, 166, 75, 129, 119, 93, 143, 129, 74, 47, 66, 70, 104, 235, 125, 238, 174, 136, 30, 135, 253, 177, 124, 19, 155, 153, 123, 56, 112, 29, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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