Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32c941fc79fa460695e59a497ea2a33f122d9b436ba6132f51889fb9d13fe4d

Tx prefix hash: 602f4606aa3b959dd6fb4d2b69b789fd4c77144e7457458c4b86acd43afce8b4
Tx public key: 8af0054384bdae47d8a9b8aa16b399c4bac2775a6b92e38406609110453d5fe8
Timestamp: 1720675283 Timestamp [UCT]: 2024-07-11 05:21:23 Age [y:d:h:m:s]: 00:294:21:09:25
Block: 1063165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210686 RingCT/type: yes/0
Extra: 018af0054384bdae47d8a9b8aa16b399c4bac2775a6b92e38406609110453d5fe802110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d040bd8016e1de64d9bd8d795d3d8238cf126b6454dffb782f799bfe4da6594e 0.600000000000 1533680 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": 1063175, "vin": [ { "gen": { "height": 1063165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d040bd8016e1de64d9bd8d795d3d8238cf126b6454dffb782f799bfe4da6594e" } } ], "extra": [ 1, 138, 240, 5, 67, 132, 189, 174, 71, 216, 169, 184, 170, 22, 179, 153, 196, 186, 194, 119, 90, 107, 146, 227, 132, 6, 96, 145, 16, 69, 61, 95, 232, 2, 17, 0, 0, 0, 11, 233, 20, 221, 21, 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