Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8bc07fbacfaac4d39775264efcf158f64a0cbda24a41808e80f8fa6dce8127c

Tx prefix hash: 08c69a7c764098df0c746e5b58e2e56806f6e9810d06dab42c08d4d005af142a
Tx public key: 9e785edbde364f6ab2eba9e326a5c698e20d2fdb58737073230be0a0baaf97cb
Timestamp: 1713152291 Timestamp [UCT]: 2024-04-15 03:38:11 Age [y:d:h:m:s]: 00:336:08:44:32
Block: 1000762 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240504 RingCT/type: yes/0
Extra: 019e785edbde364f6ab2eba9e326a5c698e20d2fdb58737073230be0a0baaf97cb0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 93305b28da1704e39d5203a51810ceaa9945dc1a6dd012bf9e1eadff40237c34 0.600000000000 1461262 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 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": 1000772, "vin": [ { "gen": { "height": 1000762 } } ], "vout": [ { "amount": 600000000, "target": { "key": "93305b28da1704e39d5203a51810ceaa9945dc1a6dd012bf9e1eadff40237c34" } } ], "extra": [ 1, 158, 120, 94, 219, 222, 54, 79, 106, 178, 235, 169, 227, 38, 165, 198, 152, 226, 13, 47, 219, 88, 115, 112, 115, 35, 11, 224, 160, 186, 175, 151, 203, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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