Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0322cb0b8f3506183f23722b7e490910e1092e4178d28122a5f12c4ac65a9580

Tx prefix hash: 60253e3cca06c4627ccb56f8595f62824f1f305a93f16903f6362ffb7f374f4b
Tx public key: 4fdf7aea16fb560aed5b727eb22e35e402478109dd84e49d316ee9b5d7cf37c4
Timestamp: 1763276865 Timestamp [UCT]: 2025-11-16 07:07:45 Age [y:d:h:m:s]: 00:078:07:05:08
Block: 1413214 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55891 RingCT/type: yes/0
Extra: 014fdf7aea16fb560aed5b727eb22e35e402478109dd84e49d316ee9b5d7cf37c40211000000054e7bfc09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef187719cea0ec85122e16e7b72049fe639383615e571a405f84029c639ec846 0.600000000000 1901691 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": 1413224, "vin": [ { "gen": { "height": 1413214 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef187719cea0ec85122e16e7b72049fe639383615e571a405f84029c639ec846" } } ], "extra": [ 1, 79, 223, 122, 234, 22, 251, 86, 10, 237, 91, 114, 126, 178, 46, 53, 228, 2, 71, 129, 9, 221, 132, 228, 157, 49, 110, 233, 181, 215, 207, 55, 196, 2, 17, 0, 0, 0, 5, 78, 123, 252, 9, 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