Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6cb433fc737caee249961825c25ed4940451d41dacd8d1a1efb1561dc16abc45

Tx prefix hash: 3a50282dd4b1b869c5b50748ed196f4bc354a9bc4b06faa86ad9a198ca7c491a
Tx public key: d56acc3b12f69e1b45d9148f34c35bb60065b9a0bff8ea2dca3e5a16ffc71b2d
Timestamp: 1772060060 Timestamp [UTC]: 2026-02-25 22:54:20 Age [y:d:h:m:s]: 00:265:12:44:32
Block: 1485828 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195277 RingCT/type: yes/0
Extra: 01d56acc3b12f69e1b45d9148f34c35bb60065b9a0bff8ea2dca3e5a16ffc71b2d021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b1528c4a2a0b35f8d91e8cf1421ee79499be191298b9c7031fe600c21b3797e9 0.000600000000 1975268 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": 1485838, "vin": [ { "gen": { "height": 1485828 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1528c4a2a0b35f8d91e8cf1421ee79499be191298b9c7031fe600c21b3797e9" } } ], "extra": [ 1, 213, 106, 204, 59, 18, 246, 158, 27, 69, 217, 20, 143, 52, 195, 91, 182, 0, 101, 185, 160, 191, 248, 234, 45, 202, 62, 90, 22, 255, 199, 27, 45, 2, 17, 0, 0, 0, 4, 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: