Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2aaac8a8ea5cc9d9cf1445ceed39e7053892818899ee1d0ab09afd337952f576

Tx prefix hash: 4f868657f8b3cbf7516d00fd7adc7e38e5fbbb922cd2cfc6154a17854e0de721
Tx public key: 693c707bba4c27b78e4d69f3899340a60bde7e3361435c06cf6bb19913e82a19
Timestamp: 1760754710 Timestamp [UTC]: 2025-10-18 02:31:50 Age [y:d:h:m:s]: 01:028:07:11:25
Block: 1392326 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286477 RingCT/type: yes/0
Extra: 01693c707bba4c27b78e4d69f3899340a60bde7e3361435c06cf6bb19913e82a190211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 44b4b5188298897effd5c77c38b4d57f2e8efb8390e8827f6fba3d23f743fd77 0.000600000000 1880577 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": 1392336, "vin": [ { "gen": { "height": 1392326 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44b4b5188298897effd5c77c38b4d57f2e8efb8390e8827f6fba3d23f743fd77" } } ], "extra": [ 1, 105, 60, 112, 123, 186, 76, 39, 183, 142, 77, 105, 243, 137, 147, 64, 166, 11, 222, 126, 51, 97, 67, 92, 6, 207, 107, 177, 153, 19, 232, 42, 25, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: