Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b03a852da584ad6b1a7fc0914a6a14f932218ce379ad4e2f8bfc64ab606e7c1a

Tx prefix hash: 687d7b2abef868a091b79ed6b778ae491c95925f7f52e37996c2f6930f710bcc
Tx public key: 50c1aad02ee0feca9c21b9ef5667fb9b191891732212e20159dffb5f5c48dc0c
Timestamp: 1639493994 Timestamp [UTC]: 2021-12-14 14:59:54 Age [y:d:h:m:s]: 04:154:16:55:12
Block: 395406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1140313 RingCT/type: yes/0
Extra: 0150c1aad02ee0feca9c21b9ef5667fb9b191891732212e20159dffb5f5c48dc0c02110000000606faf294000000000000000000

1 output(s) for total of 0.030050807004 xmr

stealth address amount amount idx tag
00: 6e7f521c693f6e5bc5ec7c13088234c7a26b8ff8702931769ae06b6a39372d82 0.030050807004 793313 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": 395416, "vin": [ { "gen": { "height": 395406 } } ], "vout": [ { "amount": 30050807004, "target": { "key": "6e7f521c693f6e5bc5ec7c13088234c7a26b8ff8702931769ae06b6a39372d82" } } ], "extra": [ 1, 80, 193, 170, 208, 46, 224, 254, 202, 156, 33, 185, 239, 86, 103, 251, 155, 25, 24, 145, 115, 34, 18, 226, 1, 89, 223, 251, 95, 92, 72, 220, 12, 2, 17, 0, 0, 0, 6, 6, 250, 242, 148, 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: