Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 23fa2caf8acea17285893ceb33cbd60f300962bf773d3c1e828b928c5e73f9f3

Tx prefix hash: c598a847aa35ebd4918bc2cf49141ec90e29678b90111174a4f7bd688659206a
Tx public key: 081c3beb6fd8348b8ebc98e49825920c556c2bc074d2daa83d06ca416bf9a251
Timestamp: 1574753729 Timestamp [UCT]: 2019-11-26 07:35:29 Age [y:d:h:m:s]: 05:004:11:09:05
Block: 17732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1146006 RingCT/type: yes/0
Extra: 01081c3beb6fd8348b8ebc98e49825920c556c2bc074d2daa83d06ca416bf9a2510211000000015ce78bfa000000000000000000

1 output(s) for total of 536.101970161000 dcy

stealth address amount amount idx
00: df5a15540b24aae8524ce385a78b2576b79c27683214f3cfdfe8168c06b00fb7 536.101970161000 26196 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": 17742, "vin": [ { "gen": { "height": 17732 } } ], "vout": [ { "amount": 536101970161, "target": { "key": "df5a15540b24aae8524ce385a78b2576b79c27683214f3cfdfe8168c06b00fb7" } } ], "extra": [ 1, 8, 28, 59, 235, 111, 216, 52, 139, 142, 188, 152, 228, 152, 37, 146, 12, 85, 108, 43, 192, 116, 210, 218, 168, 61, 6, 202, 65, 107, 249, 162, 81, 2, 17, 0, 0, 0, 1, 92, 231, 139, 250, 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