Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5e328e98e27f73367a9f0e0d62a100e8011750345da8d2a3a3c2d634144f5d6

Tx prefix hash: aae4af3482f92a767c74f8d2e1db07c526af0181d512e504468deb726c811ba8
Tx public key: c74efb6e2c186ff590e2d7e8e2bf5142b13fe69ef60b3ae1d9fd65f604c76cc1
Timestamp: 1769788426 Timestamp [UTC]: 2026-01-30 15:53:46 Age [y:d:h:m:s]: 00:296:02:48:22
Block: 1466994 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216500 RingCT/type: yes/0
Extra: 01c74efb6e2c186ff590e2d7e8e2bf5142b13fe69ef60b3ae1d9fd65f604c76cc102110000000a215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 61a9d18f708b557a979159e35df5293e74fc6b0a705969a95778de4ed69e3d42 0.000600000000 1956234 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": 1467004, "vin": [ { "gen": { "height": 1466994 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a9d18f708b557a979159e35df5293e74fc6b0a705969a95778de4ed69e3d42" } } ], "extra": [ 1, 199, 78, 251, 110, 44, 24, 111, 245, 144, 226, 215, 232, 226, 191, 81, 66, 177, 63, 230, 158, 246, 11, 58, 225, 217, 253, 101, 246, 4, 199, 108, 193, 2, 17, 0, 0, 0, 10, 33, 91, 191, 137, 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: