Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c044b22c5b72cfaa578b9e4919804174df0b5cdf97f1a6e4330290cddca6099

Tx prefix hash: 7aa3426a438c36d11719a7620f52ee0c8f3679334c20c61ee29e1091ad5aa3ce
Tx public key: 86fa9a1ff66aa735f3944cc08f9814a01f26825d0e8a4a802a174076c1188183
Timestamp: 1734735507 Timestamp [UCT]: 2024-12-20 22:58:27 Age [y:d:h:m:s]: 00:019:02:57:20
Block: 1179636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13647 RingCT/type: yes/0
Extra: 0186fa9a1ff66aa735f3944cc08f9814a01f26825d0e8a4a802a174076c1188183021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52567673b8f788b5b37f559a9d3cd2d052db04a91fa43c0bd403a4a8e1e4de01 0.600000000000 1666035 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": 1179646, "vin": [ { "gen": { "height": 1179636 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52567673b8f788b5b37f559a9d3cd2d052db04a91fa43c0bd403a4a8e1e4de01" } } ], "extra": [ 1, 134, 250, 154, 31, 246, 106, 167, 53, 243, 148, 76, 192, 143, 152, 20, 160, 31, 38, 130, 93, 14, 138, 74, 128, 42, 23, 64, 118, 193, 24, 129, 131, 2, 17, 0, 0, 0, 1, 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