Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d67d668b489c2ff7ec3f067273c286b6a0829d3b99c7e9d9259b97600d8aeea

Tx prefix hash: 41d0fac9aaca1d6bc6967b0973dc825cde7acf92af72015c413fa43e604f91aa
Tx public key: 75df89567043fc809388c8a508ba3da17138e36f8cbcb9bfd00300648fdd545e
Timestamp: 1635363124 Timestamp [UCT]: 2021-10-27 19:32:04 Age [y:d:h:m:s]: 04:004:05:57:04
Block: 361745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1039863 RingCT/type: yes/0
Extra: 0175df89567043fc809388c8a508ba3da17138e36f8cbcb9bfd00300648fdd545e02110000005242b3953e000000000000000000

1 output(s) for total of 38.850503841000 dcy

stealth address amount amount idx
00: 1515c23a7306a9c02fcc2ec5a117a2ee801c51ffaf9eb5e28353adb40de68e8a 38.850503841000 735839 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": 361755, "vin": [ { "gen": { "height": 361745 } } ], "vout": [ { "amount": 38850503841, "target": { "key": "1515c23a7306a9c02fcc2ec5a117a2ee801c51ffaf9eb5e28353adb40de68e8a" } } ], "extra": [ 1, 117, 223, 137, 86, 112, 67, 252, 128, 147, 136, 200, 165, 8, 186, 61, 161, 113, 56, 227, 111, 140, 188, 185, 191, 208, 3, 0, 100, 143, 221, 84, 94, 2, 17, 0, 0, 0, 82, 66, 179, 149, 62, 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