Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79ccdf4bb7b642578ee006ff94839344e7e07d7cbddaadebd5a34b6dbd48f05c

Tx prefix hash: 2fda31c8d219195b69bedf998a79765817f30f0508c38f212444aee0abe429e8
Tx public key: 0be0d2425e8cdb77115e2de1637be9afe8483b28a07d7347e3d52fa93c3f42f8
Timestamp: 1705451323 Timestamp [UCT]: 2024-01-17 00:28:43 Age [y:d:h:m:s]: 01:097:19:51:05
Block: 936912 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331033 RingCT/type: yes/0
Extra: 010be0d2425e8cdb77115e2de1637be9afe8483b28a07d7347e3d52fa93c3f42f802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7f3ec480024675a69609c903385aabd8721b3f70a6c7a8c73cf045ff36b4dcc2 0.600000000000 1394956 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": 936922, "vin": [ { "gen": { "height": 936912 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f3ec480024675a69609c903385aabd8721b3f70a6c7a8c73cf045ff36b4dcc2" } } ], "extra": [ 1, 11, 224, 210, 66, 94, 140, 219, 119, 17, 94, 45, 225, 99, 123, 233, 175, 232, 72, 59, 40, 160, 125, 115, 71, 227, 213, 47, 169, 60, 63, 66, 248, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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