Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ce08e04f55c81426001e66786e69b49d8ec4aabf83fab8caf7002685e6d068

Tx prefix hash: 3ea08ef71a775396a793044d2025463d06de207c5c5a917bfebac2f8d482b93c
Tx public key: f0ea33e6c2d7a21fac18c9fa487e1a87bea5ad3899f9077f23214c9e901331bf
Timestamp: 1707309617 Timestamp [UCT]: 2024-02-07 12:40:17 Age [y:d:h:m:s]: 01:020:20:34:50
Block: 952341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 275931 RingCT/type: yes/0
Extra: 01f0ea33e6c2d7a21fac18c9fa487e1a87bea5ad3899f9077f23214c9e901331bf02110000000410a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c40fa98d439b9722805d63b10373d725cbc16aaab3ce09a47a0a99e9bec75a1 0.600000000000 1411267 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": 952351, "vin": [ { "gen": { "height": 952341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c40fa98d439b9722805d63b10373d725cbc16aaab3ce09a47a0a99e9bec75a1" } } ], "extra": [ 1, 240, 234, 51, 230, 194, 215, 162, 31, 172, 24, 201, 250, 72, 126, 26, 135, 190, 165, 173, 56, 153, 249, 7, 127, 35, 33, 76, 158, 144, 19, 49, 191, 2, 17, 0, 0, 0, 4, 16, 161, 116, 143, 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