Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7bdd1da399e416eb52b889e22d3f2f9b0c68d3885b66c0c50a07471eca65f6

Tx prefix hash: c2227de533dad7a170a7de352c28a02bef149d68d7851d6614234e6580c5edac
Tx public key: 353c070e87b279bd7e5b8b5199a6377b41878e0d5250627d385079cd72184df8
Timestamp: 1761769512 Timestamp [UTC]: 2025-10-29 20:25:12 Age [y:d:h:m:s]: 00:197:10:28:58
Block: 1400738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133450 RingCT/type: yes/0
Extra: 01353c070e87b279bd7e5b8b5199a6377b41878e0d5250627d385079cd72184df802110000000625a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3782d0ad44bf9c35b68cf36f24b83c5b6133219c9d57c19e85aa622a76b3ac5a 0.000600000000 1889055 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": 1400748, "vin": [ { "gen": { "height": 1400738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3782d0ad44bf9c35b68cf36f24b83c5b6133219c9d57c19e85aa622a76b3ac5a" } } ], "extra": [ 1, 53, 60, 7, 14, 135, 178, 121, 189, 126, 91, 139, 81, 153, 166, 55, 123, 65, 135, 142, 13, 82, 80, 98, 125, 56, 80, 121, 205, 114, 24, 77, 248, 2, 17, 0, 0, 0, 6, 37, 163, 90, 15, 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: