Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae0842e97f18a86f80717dc70e672f2c7acfb76dd3f27de2fc89e0b1eba0e304

Tx prefix hash: 018769a1e185df2f45884416fdf92258ae39282c6da8a8980a6699048e872161
Tx public key: ad1de9ed7e3fc417453c5d25a79c1a3e6c34bab2a5ae999aa887b69f66ffbd8e
Timestamp: 1740438692 Timestamp [UTC]: 2025-02-24 23:11:32 Age [y:d:h:m:s]: 01:140:11:30:56
Block: 1226531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356305 RingCT/type: yes/0
Extra: 01ad1de9ed7e3fc417453c5d25a79c1a3e6c34bab2a5ae999aa887b69f66ffbd8e021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea2d7f1653caf8486634065953a8cdf4040e4ba15ceeeb341c75988aa7152454 0.000600000000 1713402 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 dinastycoin-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": 1226541, "vin": [ { "gen": { "height": 1226531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea2d7f1653caf8486634065953a8cdf4040e4ba15ceeeb341c75988aa7152454" } } ], "extra": [ 1, 173, 29, 233, 237, 126, 63, 196, 23, 69, 60, 93, 37, 167, 156, 26, 62, 108, 52, 186, 178, 165, 174, 153, 154, 168, 135, 182, 159, 102, 255, 189, 142, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: