Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc90fc245a69512a203ededf4aadf5b482be92a6bf068fcf1cd74a833cf2cd95

Tx prefix hash: 200837192628260b76313d814c62da690a694e049a6ad3e6a5bf25ed5e3a97e0
Tx public key: 5e1cf5576eb0ba2c786608efcdeaa7aaf66810186401a6dd9f31080913101cd4
Timestamp: 1774139346 Timestamp [UTC]: 2026-03-22 00:29:06 Age [y:d:h:m:s]: 00:240:05:12:56
Block: 1502990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177185 RingCT/type: yes/0
Extra: 015e1cf5576eb0ba2c786608efcdeaa7aaf66810186401a6dd9f31080913101cd4021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ea22587ddb9029b5e3fc3c84f78aa7480fc7aa7b2f6f7dc20b4ed80fce1959c3 0.000600000000 1992694 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": 1503000, "vin": [ { "gen": { "height": 1502990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea22587ddb9029b5e3fc3c84f78aa7480fc7aa7b2f6f7dc20b4ed80fce1959c3" } } ], "extra": [ 1, 94, 28, 245, 87, 110, 176, 186, 44, 120, 102, 8, 239, 205, 234, 167, 170, 246, 104, 16, 24, 100, 1, 166, 221, 159, 49, 8, 9, 19, 16, 28, 212, 2, 17, 0, 0, 0, 4, 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: