Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 350af691d2bc8ddb1d47458ea8ce80b2adcb0e4297c5ad6cf1a3dfd8810743c4

Tx prefix hash: 4797b42f755923d7d2336ef97bf9719792a4e1f83e20f953919e6419240e9658
Tx public key: a92955b3c23e962ddc3921b479001ed53935762d1480b3c68ac4d17fa2de81dd
Timestamp: 1773463434 Timestamp [UTC]: 2026-03-14 04:43:54 Age [y:d:h:m:s]: 00:247:00:38:08
Block: 1497406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182023 RingCT/type: yes/0
Extra: 01a92955b3c23e962ddc3921b479001ed53935762d1480b3c68ac4d17fa2de81dd021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 02421cfa95d40a8805425467341df43500b4f461ebd83f39f5b41fb5bd79b9b6 0.000600000000 1987042 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": 1497416, "vin": [ { "gen": { "height": 1497406 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02421cfa95d40a8805425467341df43500b4f461ebd83f39f5b41fb5bd79b9b6" } } ], "extra": [ 1, 169, 41, 85, 179, 194, 62, 150, 45, 220, 57, 33, 180, 121, 0, 30, 213, 57, 53, 118, 45, 20, 128, 179, 198, 138, 196, 209, 127, 162, 222, 129, 221, 2, 17, 0, 0, 0, 2, 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: