Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 641a339fc459e712da7fba966077d8a9f9dd1fc839034b784db067d178e3f936

Tx prefix hash: d19960fded236ee5f4ef2152e1aeb6dbe55b20a8815230608ba2fa7f3f4d235c
Tx public key: 1f64e3ccfae858ec3dcfc17cc846cfc91d35455ff7b7a13c0010ef9e7bb5ecd7
Timestamp: 1740803215 Timestamp [UCT]: 2025-03-01 04:26:55 Age [y:d:h:m:s]: 00:264:19:57:27
Block: 1229556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187026 RingCT/type: yes/0
Extra: 011f64e3ccfae858ec3dcfc17cc846cfc91d35455ff7b7a13c0010ef9e7bb5ecd7021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef656b8d658a5381eb603c638c8c35fd201bf48f5cf579a3b48c161cf7f16e31 0.600000000000 1716443 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": 1229566, "vin": [ { "gen": { "height": 1229556 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef656b8d658a5381eb603c638c8c35fd201bf48f5cf579a3b48c161cf7f16e31" } } ], "extra": [ 1, 31, 100, 227, 204, 250, 232, 88, 236, 61, 207, 193, 124, 200, 70, 207, 201, 29, 53, 69, 95, 247, 183, 161, 60, 0, 16, 239, 158, 123, 181, 236, 215, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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