Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b17dd747ffa285ddb1dc8b626a0fdc884a9ad810b50f97aaa32f7baba668bbdb

Tx prefix hash: 120af78634dfe4bc741fa90a5f8c068b03c2b026794b6af2d3a178b528f77374
Tx public key: cfcc62fffa247f90276e44fb09a7b092309d5d09675f23c91fbb34d11649927d
Timestamp: 1701297666 Timestamp [UCT]: 2023-11-29 22:41:06 Age [y:d:h:m:s]: 01:140:07:31:18
Block: 902489 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361464 RingCT/type: yes/0
Extra: 01cfcc62fffa247f90276e44fb09a7b092309d5d09675f23c91fbb34d11649927d02110000000175e3f0e9000000000000000000

1 output(s) for total of 0.627594721000 dcy

stealth address amount amount idx
00: 4cfd731837e87159b157b9e8c20e27c95c07883b68ae26f812217e96e7eb6be3 0.627594721000 1359132 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": 902499, "vin": [ { "gen": { "height": 902489 } } ], "vout": [ { "amount": 627594721, "target": { "key": "4cfd731837e87159b157b9e8c20e27c95c07883b68ae26f812217e96e7eb6be3" } } ], "extra": [ 1, 207, 204, 98, 255, 250, 36, 127, 144, 39, 110, 68, 251, 9, 167, 176, 146, 48, 157, 93, 9, 103, 95, 35, 201, 31, 187, 52, 209, 22, 73, 146, 125, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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