Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 411a3f062d66221118ac6efc28b051d71325346bd39de790b650fd7304bf7c9c

Tx prefix hash: dfba557f860b92c8d0c2f042ecf1ae336d31e85787a9fdd3ccf003fed0ca1848
Tx public key: 52aaf547983c50cfde7f1bf4f8a7c51b6eb165bc82945730a8ef42600e056b75
Timestamp: 1715699932 Timestamp [UCT]: 2024-05-14 15:18:52 Age [y:d:h:m:s]: 00:338:18:55:27
Block: 1021914 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242161 RingCT/type: yes/0
Extra: 0152aaf547983c50cfde7f1bf4f8a7c51b6eb165bc82945730a8ef42600e056b75021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef8d22b9206e073627d33e32c0b0849632114e7fd7f9c3e87d6f480968be088a 0.600000000000 1486363 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": 1021924, "vin": [ { "gen": { "height": 1021914 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef8d22b9206e073627d33e32c0b0849632114e7fd7f9c3e87d6f480968be088a" } } ], "extra": [ 1, 82, 170, 245, 71, 152, 60, 80, 207, 222, 127, 27, 244, 248, 167, 197, 27, 110, 177, 101, 188, 130, 148, 87, 48, 168, 239, 66, 96, 14, 5, 107, 117, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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