Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69934dee5208def720be02e4482e00c93d52f7627e717c504e7ee61b4429b603

Tx prefix hash: 0a767f8c9dd39f2fed40a8016d8a49e3003a425ec68eca242b4e493f306432d2
Tx public key: 040af666a10cf89d1cde2359d0a3da24648b3a8586c0b9962cd3ea56066dbd1a
Timestamp: 1748211760 Timestamp [UTC]: 2025-05-25 22:22:40 Age [y:d:h:m:s]: 01:086:18:49:20
Block: 1290909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326706 RingCT/type: yes/0
Extra: 01040af666a10cf89d1cde2359d0a3da24648b3a8586c0b9962cd3ea56066dbd1a0211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4ee2289a949d303aad54d1f4f6e51a179df5a6edb4b78a2360bfcb517de6319 0.000600000000 1778380 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": 1290919, "vin": [ { "gen": { "height": 1290909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ee2289a949d303aad54d1f4f6e51a179df5a6edb4b78a2360bfcb517de6319" } } ], "extra": [ 1, 4, 10, 246, 102, 161, 12, 248, 157, 28, 222, 35, 89, 208, 163, 218, 36, 100, 139, 58, 133, 134, 192, 185, 150, 44, 211, 234, 86, 6, 109, 189, 26, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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: