Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5369c75cf8ae4293919d23f006608a19d64cf061ef2f2628f9fee63a2c5486a4

Tx prefix hash: feb3cba71737bd2617724ea16341d5041765b7993277abe597c1c39f952d39cd
Tx public key: cf64fac0cabb0c9a4a7a41f381b572d4b1030b0e20b064dba100637a267da450
Timestamp: 1763138502 Timestamp [UTC]: 2025-11-14 16:41:42 Age [y:d:h:m:s]: 00:282:19:56:18
Block: 1412065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207878 RingCT/type: yes/0
Extra: 01cf64fac0cabb0c9a4a7a41f381b572d4b1030b0e20b064dba100637a267da450021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cd81bb977841d2ea92b423bfa6b4ea47d65a1f625131f0f631f6a6f9d8a3ea3a 0.000600000000 1900530 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": 1412075, "vin": [ { "gen": { "height": 1412065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd81bb977841d2ea92b423bfa6b4ea47d65a1f625131f0f631f6a6f9d8a3ea3a" } } ], "extra": [ 1, 207, 100, 250, 192, 202, 187, 12, 154, 74, 122, 65, 243, 129, 181, 114, 212, 177, 3, 11, 14, 32, 176, 100, 219, 161, 0, 99, 122, 38, 125, 164, 80, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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: