Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29e39312a778f4669cea0e56607be43b4d92059a336650bf9314f2985758c18d

Tx prefix hash: ea269d90118cc7137449f5ef5fcaa5d035f1ad363c113f9101f4de1e8c122b67
Tx public key: 6cc05fbaceebd4f3ec9faa526f43b20b1cbb217a4220e257568f299fa1b529c0
Timestamp: 1703798073 Timestamp [UCT]: 2023-12-28 21:14:33 Age [y:d:h:m:s]: 01:327:20:08:08
Block: 923232 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 493145 RingCT/type: yes/0
Extra: 016cc05fbaceebd4f3ec9faa526f43b20b1cbb217a4220e257568f299fa1b529c00211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0708549f13b162a26a3519df3b0e1fdce02b6f6336060be07f87d6e1351d941 0.600000000000 1380960 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": 923242, "vin": [ { "gen": { "height": 923232 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0708549f13b162a26a3519df3b0e1fdce02b6f6336060be07f87d6e1351d941" } } ], "extra": [ 1, 108, 192, 95, 186, 206, 235, 212, 243, 236, 159, 170, 82, 111, 67, 178, 11, 28, 187, 33, 122, 66, 32, 226, 87, 86, 143, 41, 159, 161, 181, 41, 192, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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