Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eab3a32b9d6000af833fd90a7540ec7025823df4b7ad777edfd8d05de7362c92

Tx prefix hash: 20ce871b124d05baa85141878f63408f7cae9e2034e1e8c1bde294bf35ab020b
Tx public key: 36fa364aef02f0b19bb21ae1b3cd631737d7e0160b4e350ce40c4947db4d45cb
Timestamp: 1764738758 Timestamp [UCT]: 2025-12-03 05:12:38 Age [y:d:h:m:s]: 00:001:08:22:01
Block: 1425328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 987 RingCT/type: yes/0
Extra: 0136fa364aef02f0b19bb21ae1b3cd631737d7e0160b4e350ce40c4947db4d45cb021100000003defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72d331715695d361b1bdc795a87010b492fe411b02fd8100c8c85ea5f8de2f1f 0.600000000000 1913961 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": 1425338, "vin": [ { "gen": { "height": 1425328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72d331715695d361b1bdc795a87010b492fe411b02fd8100c8c85ea5f8de2f1f" } } ], "extra": [ 1, 54, 250, 54, 74, 239, 2, 240, 177, 155, 178, 26, 225, 179, 205, 99, 23, 55, 215, 224, 22, 11, 78, 53, 12, 228, 12, 73, 71, 219, 77, 69, 203, 2, 17, 0, 0, 0, 3, 222, 251, 143, 24, 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