Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 220c0f63f24fc44f5353038db1f60c3f4a2c6b0a96eb020d20c5fa7d9a989dcd

Tx prefix hash: 9915af42804a5ac54b9906e65e32b06df1ea115f52b0b41550fca99797a332ce
Tx public key: 0ad127bc6607eb931565238e9fb428e98a6e4b6f75c63a15f01df2c0f4d9c106
Timestamp: 1770499611 Timestamp [UTC]: 2026-02-07 21:26:51 Age [y:d:h:m:s]: 00:281:09:53:40
Block: 1472912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206577 RingCT/type: yes/0
Extra: 010ad127bc6607eb931565238e9fb428e98a6e4b6f75c63a15f01df2c0f4d9c106021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e7e191e3735ab5850ce94d796d722d23c590d31054ea318b59581023b8e62a92 0.000600000000 1962194 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": 1472922, "vin": [ { "gen": { "height": 1472912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7e191e3735ab5850ce94d796d722d23c590d31054ea318b59581023b8e62a92" } } ], "extra": [ 1, 10, 209, 39, 188, 102, 7, 235, 147, 21, 101, 35, 142, 159, 180, 40, 233, 138, 110, 75, 111, 117, 198, 58, 21, 240, 29, 242, 192, 244, 217, 193, 6, 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: