Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfb5acf925273ecb2b8af3aa1fecef4a5df6c5eb173373b02e3f7d7f1763efa1

Tx prefix hash: 920e7f437e885776d0c85c11a35bdf676ca911008f1204c1c81c7a2365030f02
Tx public key: 5aaad45eb51852ad56b8469de362e3891e0d694adaabc4d249982b36a797fe5e
Timestamp: 1722239915 Timestamp [UCT]: 2024-07-29 07:58:35 Age [y:d:h:m:s]: 00:252:18:56:00
Block: 1076126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180559 RingCT/type: yes/0
Extra: 015aaad45eb51852ad56b8469de362e3891e0d694adaabc4d249982b36a797fe5e021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f8272ffbde3508449ca17e4577f721cf2b367d3adba720140f9a6cfab7e65ca 0.600000000000 1548661 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": 1076136, "vin": [ { "gen": { "height": 1076126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f8272ffbde3508449ca17e4577f721cf2b367d3adba720140f9a6cfab7e65ca" } } ], "extra": [ 1, 90, 170, 212, 94, 181, 24, 82, 173, 86, 184, 70, 157, 227, 98, 227, 137, 30, 13, 105, 74, 218, 171, 196, 210, 73, 152, 43, 54, 167, 151, 254, 94, 2, 17, 0, 0, 0, 9, 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