Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c2d6644513bc755fd3d05d6fc81b7dbb3525e1aa701a03e9339f4518ad6bf074

Tx prefix hash: 664fe6f6ca1173eca03eec7e510075395446d6c722147e9b473506673c3ad3ae
Tx public key: 2261118af452f2c66453c3cc81e8162f6b548af56b343ed8f4a9a26fb4aa1a59
Timestamp: 1577785960 Timestamp [UTC]: 2019-12-31 09:52:40 Age [y:d:h:m:s]: 06:326:22:04:54
Block: 35585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1647682 RingCT/type: yes/0
Extra: 012261118af452f2c66453c3cc81e8162f6b548af56b343ed8f4a9a26fb4aa1a590211000000054943cd9f000000000000000000

1 output(s) for total of 0.467835288304 xmr

stealth address amount amount idx tag
00: a45e47a16e4be29138d1d6d3dc1191b9699a99f5bc9bf8fb66667f36b1d4bf8c 0.467835288304 60084 of 0 -

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": 35595, "vin": [ { "gen": { "height": 35585 } } ], "vout": [ { "amount": 467835288304, "target": { "key": "a45e47a16e4be29138d1d6d3dc1191b9699a99f5bc9bf8fb66667f36b1d4bf8c" } } ], "extra": [ 1, 34, 97, 17, 138, 244, 82, 242, 198, 100, 83, 195, 204, 129, 232, 22, 47, 107, 84, 138, 245, 107, 52, 62, 216, 244, 169, 162, 111, 180, 170, 26, 89, 2, 17, 0, 0, 0, 5, 73, 67, 205, 159, 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: