Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64e38c4da982c81e4b7140b387b2b8e348dd68df69571387bcaee4bb74b1de1c

Tx prefix hash: 6ab35364609b84833c38f1a20fec4968a7698f6d15d5ca8732ef793bcd3f65ac
Tx public key: 6b31cd0cef322142c2f74399f05b9dd6d378ab6a0d50a09a43822079c8173430
Timestamp: 1763846724 Timestamp [UCT]: 2025-11-22 21:25:24 Age [y:d:h:m:s]: 00:004:12:40:58
Block: 1417925 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3257 RingCT/type: yes/0
Extra: 016b31cd0cef322142c2f74399f05b9dd6d378ab6a0d50a09a43822079c8173430021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe0ba80ec8e03244b03ac470e28a7fa3aa1f4ebc11a0d78d37b19ae23801ca3b 0.600000000000 1906452 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": 1417935, "vin": [ { "gen": { "height": 1417925 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0ba80ec8e03244b03ac470e28a7fa3aa1f4ebc11a0d78d37b19ae23801ca3b" } } ], "extra": [ 1, 107, 49, 205, 12, 239, 50, 33, 66, 194, 247, 67, 153, 240, 91, 157, 214, 211, 120, 171, 106, 13, 80, 160, 154, 67, 130, 32, 121, 200, 23, 52, 48, 2, 17, 0, 0, 0, 3, 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