Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 659b8f795039d4777e73a414a9ec81c15886d8867ceb6e7f53a88353278cf636

Tx prefix hash: a86bb9171e9facbf793be206641245acabba6c0cc64071006a80ae309ff97f40
Tx public key: c59b14760aeae95c26a030289b997a559a68a9151b91ee154e967f2aae8fb6eb
Timestamp: 1577739939 Timestamp [UCT]: 2019-12-30 21:05:39 Age [y:d:h:m:s]: 05:306:04:03:40
Block: 35327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1366271 RingCT/type: yes/0
Extra: 01c59b14760aeae95c26a030289b997a559a68a9151b91ee154e967f2aae8fb6eb0211000000044ac5aa02000000000000000000

1 output(s) for total of 468.757078138000 dcy

stealth address amount amount idx
00: d87b0ef846f3f17a075c0729f0f353ec7c193b6780546a044e9f5ee630142e98 468.757078138000 59501 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 dinasty-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": 35337, "vin": [ { "gen": { "height": 35327 } } ], "vout": [ { "amount": 468757078138, "target": { "key": "d87b0ef846f3f17a075c0729f0f353ec7c193b6780546a044e9f5ee630142e98" } } ], "extra": [ 1, 197, 155, 20, 118, 10, 234, 233, 92, 38, 160, 48, 40, 155, 153, 122, 85, 154, 104, 169, 21, 27, 145, 238, 21, 78, 150, 127, 42, 174, 143, 182, 235, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8