Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dce47b3e359cbe647d268cb329e14c218311e3a4c97315dc71c59eabc4aa8943

Tx prefix hash: 630132acdb1ea1ddf14acd6e0e7eebd276b02296f39a2217b505c48ec1330ab5
Tx public key: bf4a1d486cd982911769a26dfc6ca6c6fb4e8a16b172fb59bc2e34a0063e49e6
Timestamp: 1752704267 Timestamp [UTC]: 2025-07-16 22:17:47 Age [y:d:h:m:s]: 01:122:20:17:16
Block: 1326981 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352847 RingCT/type: yes/0
Extra: 01bf4a1d486cd982911769a26dfc6ca6c6fb4e8a16b172fb59bc2e34a0063e49e602110000000443846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe265221df6e1f17ea9b7c9fbec3f75347f33ec21a533f29ebc409967d5d072f 0.000600000000 1814734 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": 1326991, "vin": [ { "gen": { "height": 1326981 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe265221df6e1f17ea9b7c9fbec3f75347f33ec21a533f29ebc409967d5d072f" } } ], "extra": [ 1, 191, 74, 29, 72, 108, 217, 130, 145, 23, 105, 162, 109, 252, 108, 166, 198, 251, 78, 138, 22, 177, 114, 251, 89, 188, 46, 52, 160, 6, 62, 73, 230, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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: