Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2920f54eedd5c711ff40533e96feb37e330bedd4ebc71b70b5f1e6248fcb187

Tx prefix hash: cc521f35f960585f42307fdc2b4612e507fca1f780b6f6a954d0e60f3babbd4a
Tx public key: 289cdcf31de26e99425eece23168eebc2cffd2d520fbe5a530d1b49f1bab9538
Timestamp: 1770815581 Timestamp [UTC]: 2026-02-11 13:13:01 Age [y:d:h:m:s]: 00:279:18:15:24
Block: 1475519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 205457 RingCT/type: yes/0
Extra: 01289cdcf31de26e99425eece23168eebc2cffd2d520fbe5a530d1b49f1bab9538020866271c4f24677e55

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5225eac369f0ff24ff871948ecac70df86e18385b58df0c6b0926130646fa817 0.000600000000 1964821 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": 1475529, "vin": [ { "gen": { "height": 1475519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5225eac369f0ff24ff871948ecac70df86e18385b58df0c6b0926130646fa817" } } ], "extra": [ 1, 40, 156, 220, 243, 29, 226, 110, 153, 66, 94, 236, 226, 49, 104, 238, 188, 44, 255, 210, 213, 32, 251, 229, 165, 48, 209, 180, 159, 27, 171, 149, 56, 2, 8, 102, 39, 28, 79, 36, 103, 126, 85 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: