Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ee766e16409da0bfc33cd06cf2d4dfd9af09983efbe72880525e8bf485fb620

Tx prefix hash: 1c1c768837c82f5ae6cc8b5c2462499d0fb57bf878809d746c2d07c6883a17e3
Tx public key: b500d1aaf4d71f964351cb801f18782ae9cf0dd12a6f7650c96bb60a420f99e4
Timestamp: 1774205218 Timestamp [UTC]: 2026-03-22 18:46:58 Age [y:d:h:m:s]: 00:238:12:38:55
Block: 1503529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175964 RingCT/type: yes/0
Extra: 01b500d1aaf4d71f964351cb801f18782ae9cf0dd12a6f7650c96bb60a420f99e4021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 128347e30cf84d76b1eee2dc7e681241c489a1741f170eabf2433f27927d681d 0.000600000000 1993241 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": 1503539, "vin": [ { "gen": { "height": 1503529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "128347e30cf84d76b1eee2dc7e681241c489a1741f170eabf2433f27927d681d" } } ], "extra": [ 1, 181, 0, 209, 170, 244, 215, 31, 150, 67, 81, 203, 128, 31, 24, 120, 42, 233, 207, 13, 209, 42, 111, 118, 80, 201, 107, 182, 10, 66, 15, 153, 228, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 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: