Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37f5eb2f21d17241b86f07e16f5207a60f34dcba5d9165f94db5b6cecb3dc4e6

Tx prefix hash: 8b0dbf198cb571d5a7d0516919e226c42de7f18d1b7195956ae56edc6048438d
Tx public key: ee80eddbd5e8ab611b0059107700f5e23a2b15c044a127e611194f5fa796c5e4
Timestamp: 1716833879 Timestamp [UCT]: 2024-05-27 18:17:59 Age [y:d:h:m:s]: 00:304:08:00:30
Block: 1031318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217499 RingCT/type: yes/0
Extra: 01ee80eddbd5e8ab611b0059107700f5e23a2b15c044a127e611194f5fa796c5e40211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f569cb404c76c014f5a3e17cbe3cf1be4c2d39d8255a95d9fc24ca9e5e78e0b 0.600000000000 1499739 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": 1031328, "vin": [ { "gen": { "height": 1031318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f569cb404c76c014f5a3e17cbe3cf1be4c2d39d8255a95d9fc24ca9e5e78e0b" } } ], "extra": [ 1, 238, 128, 237, 219, 213, 232, 171, 97, 27, 0, 89, 16, 119, 0, 245, 226, 58, 43, 21, 192, 68, 161, 39, 230, 17, 25, 79, 95, 167, 150, 197, 228, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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