Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f5ad23cd007f678e44e495a40caf25ff575eb50b8b6c5a7284b8de4c3e86963

Tx prefix hash: e859bcf9a1205ef07fa1a9220da8c2b5ead436f0a90ae659024643956cb50d91
Tx public key: abcf064223f3cbc7445b4a37a9428ef4055ccb003aa0cfa59eb277a8114d5ee6
Timestamp: 1677388084 Timestamp [UCT]: 2023-02-26 05:08:04 Age [y:d:h:m:s]: 02:096:16:01:19
Block: 705158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590719 RingCT/type: yes/0
Extra: 01abcf064223f3cbc7445b4a37a9428ef4055ccb003aa0cfa59eb277a8114d5ee602110000000183600029000000000000000000

1 output(s) for total of 2.828256062000 dcy

stealth address amount amount idx
00: 60f074ffd3bd5b4cb39ecd87b41c46dd923aa37a9576c9b1b7f398783c548bb2 2.828256062000 1148849 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": 705168, "vin": [ { "gen": { "height": 705158 } } ], "vout": [ { "amount": 2828256062, "target": { "key": "60f074ffd3bd5b4cb39ecd87b41c46dd923aa37a9576c9b1b7f398783c548bb2" } } ], "extra": [ 1, 171, 207, 6, 66, 35, 243, 203, 199, 68, 91, 74, 55, 169, 66, 142, 244, 5, 92, 203, 0, 58, 160, 207, 165, 158, 178, 119, 168, 17, 77, 94, 230, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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