Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50af28fc6ff744b6c60dc1e69b10fa67883b671bf61ff48218bf356e97ea58a9

Tx prefix hash: d49ce8794806785283b8f74e4e4f8190e6ac2d364ff0288f17d282e3c1e1c9cb
Tx public key: 6722c1c3dc58ac80678581d293b261287fcc052876927162fcb3e567a91eb9b7
Timestamp: 1772719705 Timestamp [UTC]: 2026-03-05 14:08:25 Age [y:d:h:m:s]: 00:260:15:37:34
Block: 1491256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191948 RingCT/type: yes/0
Extra: 016722c1c3dc58ac80678581d293b261287fcc052876927162fcb3e567a91eb9b7021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4c5a9ab8777605f52374206c06f1f47cb963ad08e4a48a9cc10926cbd86d359b 0.000600000000 1980774 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": 1491266, "vin": [ { "gen": { "height": 1491256 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c5a9ab8777605f52374206c06f1f47cb963ad08e4a48a9cc10926cbd86d359b" } } ], "extra": [ 1, 103, 34, 193, 195, 220, 88, 172, 128, 103, 133, 129, 210, 147, 178, 97, 40, 127, 204, 5, 40, 118, 146, 113, 98, 252, 179, 229, 103, 169, 30, 185, 183, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: