Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cf94f8d8a86bb461db4888126a357cfc9310767cfb4afda3b3897e258023ba9

Tx prefix hash: 784119db1ee8876f2d7780d2990fc279eb6d8b80d0ec36bbc50eec1b6f224422
Tx public key: 948765d01ab33c787a18148c5235366353e862d036f2ea74331062fb74a0af53
Timestamp: 1751200066 Timestamp [UTC]: 2025-06-29 12:27:46 Age [y:d:h:m:s]: 01:143:03:04:55
Block: 1315207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366774 RingCT/type: yes/0
Extra: 01948765d01ab33c787a18148c5235366353e862d036f2ea74331062fb74a0af53021100000022bf51b2a2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c25b3c426282d811f6b453897ac915ea55bb60e1e293dfe05b40fd9821728d3a 0.000600000000 1802860 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": 1315217, "vin": [ { "gen": { "height": 1315207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c25b3c426282d811f6b453897ac915ea55bb60e1e293dfe05b40fd9821728d3a" } } ], "extra": [ 1, 148, 135, 101, 208, 26, 179, 60, 120, 122, 24, 20, 140, 82, 53, 54, 99, 83, 232, 98, 208, 54, 242, 234, 116, 51, 16, 98, 251, 116, 160, 175, 83, 2, 17, 0, 0, 0, 34, 191, 81, 178, 162, 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: