Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02aef3fc5f68f725371807637abad4088561989acfb26522d574bdcd906e6a5e

Tx prefix hash: 4c53baaa4656b3af95cf914130ba4b871318de873b30b7efaf202fc827fc9be3
Tx public key: 4c6949b0e9ecdbf3bb99cc0925ef1bc04b6e3ab41ef0d707b8fee2b3b6a6abf6
Timestamp: 1708114315 Timestamp [UCT]: 2024-02-16 20:11:55 Age [y:d:h:m:s]: 01:054:02:56:29
Block: 959014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299717 RingCT/type: yes/0
Extra: 014c6949b0e9ecdbf3bb99cc0925ef1bc04b6e3ab41ef0d707b8fee2b3b6a6abf60211000000013f0590f7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f40d119497965ff2c3c9c09924a89c7c98a25958b4878ce8413d8bfe6582051 0.600000000000 1418533 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": 959024, "vin": [ { "gen": { "height": 959014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f40d119497965ff2c3c9c09924a89c7c98a25958b4878ce8413d8bfe6582051" } } ], "extra": [ 1, 76, 105, 73, 176, 233, 236, 219, 243, 187, 153, 204, 9, 37, 239, 27, 192, 75, 110, 58, 180, 30, 240, 215, 7, 184, 254, 226, 179, 182, 166, 171, 246, 2, 17, 0, 0, 0, 1, 63, 5, 144, 247, 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