Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 265546eda9aed28fe07977d524b045955d833d3e91a572fb297520ec12d0cc33

Tx prefix hash: 3f95f3f4b91fe89e3fbe6aa04f7f397a05adac5639f68ca9c0548af7eff21368
Tx public key: 233df186bbe1036340e5b9a50cec68aee0ae1dc7a7111f846b6f6d51ba755aa5
Timestamp: 1736781514 Timestamp [UCT]: 2025-01-13 15:18:34 Age [y:d:h:m:s]: 00:092:06:09:38
Block: 1196537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65722 RingCT/type: yes/0
Extra: 01233df186bbe1036340e5b9a50cec68aee0ae1dc7a7111f846b6f6d51ba755aa50211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b1e1227ebebc620ef9694921cd5a27ddb704eaa0c1e8ab75328ff39c77467dd 0.600000000000 1683136 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": 1196547, "vin": [ { "gen": { "height": 1196537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b1e1227ebebc620ef9694921cd5a27ddb704eaa0c1e8ab75328ff39c77467dd" } } ], "extra": [ 1, 35, 61, 241, 134, 187, 225, 3, 99, 64, 229, 185, 165, 12, 236, 104, 174, 224, 174, 29, 199, 167, 17, 31, 132, 107, 111, 109, 81, 186, 117, 90, 165, 2, 17, 0, 0, 0, 3, 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