Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cd000db4378a50545835a65be4fecc59a99f0783f4ef5837452c337ac9e127b

Tx prefix hash: 030f86dadc83ffa36008a9c842e9b6678708be761af8b0be2f8ab78ca5c120b9
Tx public key: 960d0a295ed7e0c271c37f6d74def62c5aa81ad45e3c938375a26856b8779c9e
Timestamp: 1694214963 Timestamp [UCT]: 2023-09-08 23:16:03 Age [y:d:h:m:s]: 01:257:09:26:38
Block: 843971 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 445103 RingCT/type: yes/0
Extra: 01960d0a295ed7e0c271c37f6d74def62c5aa81ad45e3c938375a26856b8779c9e0211000000284b8f5122000000000000000000

1 output(s) for total of 0.980784951000 dcy

stealth address amount amount idx
00: e856d7afe2e7509fa37b96d7ec4a4e0a5ab2ea639646dcd87f9c30aa27e6c07f 0.980784951000 1297251 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": 843981, "vin": [ { "gen": { "height": 843971 } } ], "vout": [ { "amount": 980784951, "target": { "key": "e856d7afe2e7509fa37b96d7ec4a4e0a5ab2ea639646dcd87f9c30aa27e6c07f" } } ], "extra": [ 1, 150, 13, 10, 41, 94, 215, 224, 194, 113, 195, 127, 109, 116, 222, 246, 44, 90, 168, 26, 212, 94, 60, 147, 131, 117, 162, 104, 86, 184, 119, 156, 158, 2, 17, 0, 0, 0, 40, 75, 143, 81, 34, 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