Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c9cfd042fdbbc351c78f22cc1fef1be1ed5a66320dbd25848660bd07c2f600

Tx prefix hash: 8fcb5c82239e042f7c115f70334406b4ded97c83b1dc95478521e9d48da0fc3f
Tx public key: cdc1d5ae70b3e92df24ffc7e496c8da8048116c287ff95e5e4d6dc62195ff87e
Timestamp: 1772666041 Timestamp [UTC]: 2026-03-04 23:14:01 Age [y:d:h:m:s]: 00:259:09:48:21
Block: 1490817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190955 RingCT/type: yes/0
Extra: 01cdc1d5ae70b3e92df24ffc7e496c8da8048116c287ff95e5e4d6dc62195ff87e021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0b47266da63beb84c9cd1a5c7e1be0f4d515605c676d5ed5d2e3f98300e09080 0.000600000000 1980327 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": 1490827, "vin": [ { "gen": { "height": 1490817 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b47266da63beb84c9cd1a5c7e1be0f4d515605c676d5ed5d2e3f98300e09080" } } ], "extra": [ 1, 205, 193, 213, 174, 112, 179, 233, 45, 242, 79, 252, 126, 73, 108, 141, 168, 4, 129, 22, 194, 135, 255, 149, 229, 228, 214, 220, 98, 25, 95, 248, 126, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: