Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3e2075b21d92440227b93afec5c3d33e6aa17dbdbc47267ff32eee8e3728e5d

Tx prefix hash: 6401657fdb6b28eef3914687e5d3f9657f129123a3639e2c04ecbfb26b4f644a
Tx public key: be2b1f7414b23b21d0bf3a8d0092d0b3abeb221f8b06fb43d1e2f3dfa117e2f6
Timestamp: 1761073103 Timestamp [UTC]: 2025-10-21 18:58:23 Age [y:d:h:m:s]: 01:025:21:01:22
Block: 1394966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284788 RingCT/type: yes/0
Extra: 01be2b1f7414b23b21d0bf3a8d0092d0b3abeb221f8b06fb43d1e2f3dfa117e2f60211000000015dfbbe2a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: be84254f0aa48bd7b40444d4adf4d3087e429e45ffd70b1c4ededbaa67799036 0.000600000000 1883241 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": 1394976, "vin": [ { "gen": { "height": 1394966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be84254f0aa48bd7b40444d4adf4d3087e429e45ffd70b1c4ededbaa67799036" } } ], "extra": [ 1, 190, 43, 31, 116, 20, 178, 59, 33, 208, 191, 58, 141, 0, 146, 208, 179, 171, 235, 34, 31, 139, 6, 251, 67, 209, 226, 243, 223, 161, 23, 226, 246, 2, 17, 0, 0, 0, 1, 93, 251, 190, 42, 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: