Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba3da2c4432bcc5a721b8bdae7be4ac44b5119ee8c195bd9d4e7ea36456768e0

Tx prefix hash: c87e2efdac3d2393e7288d302c62ea6c7721bf414e9b7bb3d73ab83c5c05fe95
Tx public key: 6d7bb79ae367a5d6bd992bde03b3456ef903f51622ee852d73fcbf67b41e0fce
Timestamp: 1771519338 Timestamp [UTC]: 2026-02-19 16:42:18 Age [y:d:h:m:s]: 00:271:15:53:04
Block: 1481329 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199679 RingCT/type: yes/0
Extra: 016d7bb79ae367a5d6bd992bde03b3456ef903f51622ee852d73fcbf67b41e0fce021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 50a069e89a8746c3a1b983cd1630ba7f58ae9e6e5d480458f8396ef56ea4e00c 0.000600000000 1970705 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": 1481339, "vin": [ { "gen": { "height": 1481329 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50a069e89a8746c3a1b983cd1630ba7f58ae9e6e5d480458f8396ef56ea4e00c" } } ], "extra": [ 1, 109, 123, 183, 154, 227, 103, 165, 214, 189, 153, 43, 222, 3, 179, 69, 110, 249, 3, 245, 22, 34, 238, 133, 45, 115, 252, 191, 103, 180, 30, 15, 206, 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: