Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0165f1d338bb6fff2a08d949befc0a6a67ec97f5d96491eecc271d5653634a18

Tx prefix hash: 6ee2535c1abb046e4a13f3308db8d91bee0568e73e2502b5af5d43a838990300
Tx public key: 780b03191285d19a45c2f5e77375be0718352264de820c2685cf9f0c498d6ca5
Timestamp: 1758490373 Timestamp [UTC]: 2025-09-21 21:32:53 Age [y:d:h:m:s]: 00:210:17:44:08
Block: 1373546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142905 RingCT/type: yes/0
Extra: 01780b03191285d19a45c2f5e77375be0718352264de820c2685cf9f0c498d6ca5021100000003ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 756dd712b5902ba8e1c658731415682d9e9c29416418c223b5db53d23a1b5ee5 0.000600000000 1861631 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": 1373556, "vin": [ { "gen": { "height": 1373546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "756dd712b5902ba8e1c658731415682d9e9c29416418c223b5db53d23a1b5ee5" } } ], "extra": [ 1, 120, 11, 3, 25, 18, 133, 209, 154, 69, 194, 245, 231, 115, 117, 190, 7, 24, 53, 34, 100, 222, 130, 12, 38, 133, 207, 159, 12, 73, 141, 108, 165, 2, 17, 0, 0, 0, 3, 173, 121, 72, 208, 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: