Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1ddbdc821000cb1ea32051e6d1fde2fc883c63673602417373cae2300901d2

Tx prefix hash: 4413de808ceb2043c547a733c227ecf9c2682c70bd13317186ca3b2b10ea4a26
Tx public key: 0d25cc3a0d047e04953b68c39dee697db6f9d28fc214923241a0c0332cafeba9
Timestamp: 1761212530 Timestamp [UTC]: 2025-10-23 09:42:10 Age [y:d:h:m:s]: 01:026:23:28:48
Block: 1396115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285668 RingCT/type: yes/0
Extra: 010d25cc3a0d047e04953b68c39dee697db6f9d28fc214923241a0c0332cafeba902110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cbd1dc06fd8c450cc3710a0c3b8a4f1025b7e754377cc3a6480fe1d240799d08 0.000600000000 1884400 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": 1396125, "vin": [ { "gen": { "height": 1396115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cbd1dc06fd8c450cc3710a0c3b8a4f1025b7e754377cc3a6480fe1d240799d08" } } ], "extra": [ 1, 13, 37, 204, 58, 13, 4, 126, 4, 149, 59, 104, 195, 157, 238, 105, 125, 182, 249, 210, 143, 194, 20, 146, 50, 65, 160, 192, 51, 44, 175, 235, 169, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: