Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dadfe4a59787a75f7f471e7ece5d6c7210c8d60a30a2bb20e45e140de0069d24

Tx prefix hash: 737df7a3b30782813355085b1de38885b7c9f17f927bb1b92579731b516c0504
Tx public key: a866b181cdf9b6a9428d0d662b4f6ef0f94825e84954fcb370f1cc28eef148d2
Timestamp: 1762513974 Timestamp [UCT]: 2025-11-07 11:12:54 Age [y:d:h:m:s]: 00:046:03:35:31
Block: 1406891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33033 RingCT/type: yes/0
Extra: 01a866b181cdf9b6a9428d0d662b4f6ef0f94825e84954fcb370f1cc28eef148d202110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 778d0c5364eff9245682ee90e65e6483bca34c596ab3f4e376a48fd4b902d850 0.600000000000 1895280 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": 1406901, "vin": [ { "gen": { "height": 1406891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "778d0c5364eff9245682ee90e65e6483bca34c596ab3f4e376a48fd4b902d850" } } ], "extra": [ 1, 168, 102, 177, 129, 205, 249, 182, 169, 66, 141, 13, 102, 43, 79, 110, 240, 249, 72, 37, 232, 73, 84, 252, 179, 112, 241, 204, 40, 238, 241, 72, 210, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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