Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6c9bb59e9fd51e85a10fc93beb8921081f4548b6d10e4df6eccb3b6d626ea25

Tx prefix hash: 5eac8d763ad7addf2e8f06b7bd9945fa9fa8979ccc8dc931ed99d52cd0d1f684
Tx public key: 7819c3cecb0b5aa09174fc205586c241ff630d50f1a44dc4710ca12aea281b1d
Timestamp: 1770248513 Timestamp [UTC]: 2026-02-04 23:41:53 Age [y:d:h:m:s]: 00:281:07:40:21
Block: 1470832 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206401 RingCT/type: yes/0
Extra: 017819c3cecb0b5aa09174fc205586c241ff630d50f1a44dc4710ca12aea281b1d021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5ad634b23774bf5dec427b2114ed5224e5332f6ddd485bf2976ba281ee4270e1 0.000600000000 1960102 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": 1470842, "vin": [ { "gen": { "height": 1470832 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ad634b23774bf5dec427b2114ed5224e5332f6ddd485bf2976ba281ee4270e1" } } ], "extra": [ 1, 120, 25, 195, 206, 203, 11, 90, 160, 145, 116, 252, 32, 85, 134, 194, 65, 255, 99, 13, 80, 241, 164, 77, 196, 113, 12, 161, 42, 234, 40, 27, 29, 2, 17, 0, 0, 0, 4, 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: