Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4ddca8eced33a009af8abc8c6cd8e1053aa241310a34c1ff692932b5d58f727

Tx prefix hash: cdab9d331a3e0ed81d2b9721bf701a5d56f597caef09829a64ecb3fced318e2b
Tx public key: 13aff876d8844ae0e49d3bfdbfd94406b570af7fbef39d22117250ba581c6bae
Timestamp: 1742062730 Timestamp [UCT]: 2025-03-15 18:18:50 Age [y:d:h:m:s]: 00:298:14:48:57
Block: 1240017 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211219 RingCT/type: yes/0
Extra: 0113aff876d8844ae0e49d3bfdbfd94406b570af7fbef39d22117250ba581c6bae0211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed6b8139734428783d29f8f8be564babe6fe8f274f417dfaae07ef184d75b7db 0.600000000000 1726982 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": 1240027, "vin": [ { "gen": { "height": 1240017 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed6b8139734428783d29f8f8be564babe6fe8f274f417dfaae07ef184d75b7db" } } ], "extra": [ 1, 19, 175, 248, 118, 216, 132, 74, 224, 228, 157, 59, 253, 191, 217, 68, 6, 181, 112, 175, 127, 190, 243, 157, 34, 17, 114, 80, 186, 88, 28, 107, 174, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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