Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a9adaeb42f86a2bf067f8b4fde1eb7dc524aaad785ccb6ba9ca30fedb9560d3c

Tx prefix hash: d288db116b67d952a894e26787c6935a0b9945ba7871d2f0d0ced4e02f8c4735
Tx public key: b3de15d57861a6924e545ef6fe2f034be28267a251aca95b96745a3838e2e73b
Timestamp: 1756149177 Timestamp [UCT]: 2025-08-25 19:12:57 Age [y:d:h:m:s]: 00:124:03:06:01
Block: 1354327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88703 RingCT/type: yes/0
Extra: 01b3de15d57861a6924e545ef6fe2f034be28267a251aca95b96745a3838e2e73b0211000000022609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bcd614e3aeb1f914f918d7146c7eb46699065cae81555c61c29f7d88efbf963 0.600000000000 1842314 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": 1354337, "vin": [ { "gen": { "height": 1354327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bcd614e3aeb1f914f918d7146c7eb46699065cae81555c61c29f7d88efbf963" } } ], "extra": [ 1, 179, 222, 21, 213, 120, 97, 166, 146, 78, 84, 94, 246, 254, 47, 3, 75, 226, 130, 103, 162, 81, 172, 169, 91, 150, 116, 90, 56, 56, 226, 231, 59, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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