Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14489c4969da28d02c9380dbd093eaa41814591374a0c3e63ce20b9e3b5cd2df

Tx prefix hash: e89da2e4929a47d9875452ebc90095554ecbb83a63f6bd470e6b691e9ce95950
Tx public key: 670d8ff3813dc59c38ffced85ee793402e700ab9cb4853bfcb4bc76054a21e98
Timestamp: 1770030513 Timestamp [UTC]: 2026-02-02 11:08:33 Age [y:d:h:m:s]: 00:100:14:28:33
Block: 1469007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64245 RingCT/type: yes/0
Extra: 01670d8ff3813dc59c38ffced85ee793402e700ab9cb4853bfcb4bc76054a21e98021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 64ff4224657891035d4cca71ebdcbdca283c24234109e0726c5e7a645d6abf4e 0.000600000000 1958261 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": 1469017, "vin": [ { "gen": { "height": 1469007 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64ff4224657891035d4cca71ebdcbdca283c24234109e0726c5e7a645d6abf4e" } } ], "extra": [ 1, 103, 13, 143, 243, 129, 61, 197, 156, 56, 255, 206, 216, 94, 231, 147, 64, 46, 112, 10, 185, 203, 72, 83, 191, 203, 75, 199, 96, 84, 162, 30, 152, 2, 17, 0, 0, 0, 7, 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: