Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc09aba7fd95e2f5e18c84a02a5f8268d0d25cd7773e125aefce37b6b1f2027a

Tx prefix hash: 815f52ca46f31c5943ad6179d3a008a3f0d7f86f3bd9d230769b77bda4a39a6c
Tx public key: 4f918d4aaaa3b4f64262efa442f4133d6832c4e5504dc83a7c942a3a84a82429
Timestamp: 1753309794 Timestamp [UTC]: 2025-07-23 22:29:54 Age [y:d:h:m:s]: 00:289:23:18:14
Block: 1331944 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198688 RingCT/type: yes/0
Extra: 014f918d4aaaa3b4f64262efa442f4133d6832c4e5504dc83a7c942a3a84a82429021100000001db6acbd3000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: ddbae176f520bb7b5d74c35b651c2b7e4ae6915902c3b55845b40867953a9e0e 0.000600000000 1819741 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": 1331954, "vin": [ { "gen": { "height": 1331944 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ddbae176f520bb7b5d74c35b651c2b7e4ae6915902c3b55845b40867953a9e0e" } } ], "extra": [ 1, 79, 145, 141, 74, 170, 163, 180, 246, 66, 98, 239, 164, 66, 244, 19, 61, 104, 50, 196, 229, 80, 77, 200, 58, 124, 148, 42, 58, 132, 168, 36, 41, 2, 17, 0, 0, 0, 1, 219, 106, 203, 211, 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: