Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a366fd79249d1a50576e21e2a479e7b372c9e1b7968b5f36932f2c5415df0a1f

Tx prefix hash: 341e109a98be090814015e81ff0c0c3bb748935a4a513558ff8780200d4ed8fa
Tx public key: e4dddccd2197722f1ccdbcf7a9324b82c498712db0cde0d386b95687cb14c472
Timestamp: 1649189629 Timestamp [UTC]: 2022-04-05 20:13:49 Age [y:d:h:m:s]: 04:231:17:20:07
Block: 473926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1209568 RingCT/type: yes/0
Extra: 01e4dddccd2197722f1ccdbcf7a9324b82c498712db0cde0d386b95687cb14c472021100000007d3fcec30000000000000000000

1 output(s) for total of 0.016507703876 xmr

stealth address amount amount idx tag
00: 7974f60d83ec1ac2e22c1e6e7e8c5ac46e01523a5493e8307c24cbee171dad31 0.016507703876 893861 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": 473936, "vin": [ { "gen": { "height": 473926 } } ], "vout": [ { "amount": 16507703876, "target": { "key": "7974f60d83ec1ac2e22c1e6e7e8c5ac46e01523a5493e8307c24cbee171dad31" } } ], "extra": [ 1, 228, 221, 220, 205, 33, 151, 114, 47, 28, 205, 188, 247, 169, 50, 75, 130, 196, 152, 113, 45, 176, 205, 224, 211, 134, 185, 86, 135, 203, 20, 196, 114, 2, 17, 0, 0, 0, 7, 211, 252, 236, 48, 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: