Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db1174248fbbd006063b7b2e1104de1b1273cf272e02ac29ac48e1f2d09d36e4

Tx prefix hash: 107b8b8bc8e4dd90875e893684ef8fd74d1b07c64e38c7673a38bb1ce36c1686
Tx public key: 293f0e1b4177312dd533f0681421d6e32f4ac1c46cd226641a6669e7336a7777
Timestamp: 1740352126 Timestamp [UCT]: 2025-02-23 23:08:46 Age [y:d:h:m:s]: 00:266:17:32:51
Block: 1225818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188392 RingCT/type: yes/0
Extra: 01293f0e1b4177312dd533f0681421d6e32f4ac1c46cd226641a6669e7336a777702110000000e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 893fc423cecf3e0af056be187adb187db8b40686947e94bb8bb1a6fe8047e317 0.600000000000 1712689 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": 1225828, "vin": [ { "gen": { "height": 1225818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "893fc423cecf3e0af056be187adb187db8b40686947e94bb8bb1a6fe8047e317" } } ], "extra": [ 1, 41, 63, 14, 27, 65, 119, 49, 45, 213, 51, 240, 104, 20, 33, 214, 227, 47, 74, 193, 196, 108, 210, 38, 100, 26, 102, 105, 231, 51, 106, 119, 119, 2, 17, 0, 0, 0, 14, 31, 10, 83, 235, 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